Triple
T21307642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 421 |
E525240
|
entity |
| Predicate | boosterCodeDigit |
P508
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Atlas V 421, boosterCodeDigit, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boosterCodeDigit Context triple: [Atlas V 421, boosterCodeDigit, 2]
-
A.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
numericCompanionCode
Indicates that one entity is associated with another through a specific numeric companion code used to link or reference them.
-
C.
BDNumber
Indicates that an entity is associated with a specific BD (Business Development or similar domain-specific) identification number used to uniquely reference it.
-
D.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
-
E.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa7b2f08190bea46f0107bcc045 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.