Triple
T21305948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 411 |
E525198
|
entity |
| Predicate | familyIntroductionYear |
P143666
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Atlas V 411, familyIntroductionYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyIntroductionYear Context triple: [Atlas V 411, familyIntroductionYear, 2002]
-
A.
familyDescription
Indicates a descriptive statement that characterizes or summarizes the nature, structure, or dynamics of a family relationship.
-
B.
familyBackgroundDetail
Indicates detailed information about an entity’s family background, such as lineage, upbringing, or familial circumstances.
-
C.
childBirthYear
Indicates the calendar year in which a child of the given parent was born.
-
D.
yearOfBirth
Indicates the specific calendar year in which an entity was born.
-
E.
relationshipStartYear
Indicates the calendar year in which a particular relationship between entities was initiated.
- F. None of above. chosen
Provenance (4 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa3f90481909b212bdbf00c2bb0 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.