Triple
T21314499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 431 |
E525429
|
entity |
| Predicate | familyDesignationCode |
P134982
|
FINISHED |
| Object | 431 |
—
|
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: 431 | Statement: [Atlas V 431, familyDesignationCode, 431]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyDesignationCode Context triple: [Atlas V 431, familyDesignationCode, 431]
-
A.
familyDesignation
Indicates the specific familial role or relationship label assigned to one entity in relation to another (e.g., parent, sibling, child).
-
B.
familyCode
chosen
Indicates that two or more entities share a common family identifier or classification code that groups them as related.
-
C.
familyCodeName
Indicates a designated code name used to identify or refer to a family unit or family-related grouping.
-
D.
serviceDesignationFamily
Indicates that one service designation is part of the same family or grouping as another, reflecting a shared classification or closely related category.
-
E.
familyVariant
Indicates a relationship where one entity is a variant or version within the same family or closely related group as another entity.
- 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.