Triple
T21314500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 431 |
E525429
|
entity |
| Predicate | codeFirstDigitMeaning |
P135084
|
FINISHED |
| Object | 4-meter payload fairing |
—
|
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: 4-meter payload fairing | Statement: [Atlas V 431, codeFirstDigitMeaning, 4-meter payload fairing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeFirstDigitMeaning Context triple: [Atlas V 431, codeFirstDigitMeaning, 4-meter payload fairing]
-
A.
firstDigitEncoding
Indicates that one entity encodes or represents the first digit of another entity (such as a number, code, or identifier).
-
B.
firstCharacteristicNumeralMeaning
chosen
Indicates that the relationship specifies the meaning associated with the first characteristic numeral of an entity or concept.
-
C.
digitMeaning
Indicates that a particular digit symbol is associated with a specific numerical value or conceptual meaning.
-
D.
secondDigitRepresents
Indicates that the second digit in a numeric or coded value encodes or signifies a specific attribute, category, or meaning within that value.
-
E.
digitSymbolForOne
Indicates that something is the written or symbolic representation used to denote the numeric value one.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dce6b4081909841ac0440fca5e4 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:28 p.m.