Triple
T432774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arecibo message |
E9748
|
entity |
| Predicate | bitLength |
P4121
|
FINISHED |
| Object | 1679 bits |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1679 bits | Statement: [Arecibo message, bitLength, 1679 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitLength Context triple: [Arecibo message, bitLength, 1679 bits]
-
A.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
B.
lengthInWords
Indicates the number of words that make up the length of something, typically a text or expression.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
E.
isFeatureLength
Indicates that something (typically a film or video) has a duration long enough to be considered a full-length, standard feature.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef084840819080653004b674cba8 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.