Triple
T17390954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 551 |
E422820
|
entity |
| Predicate | configurationNumber |
P8607
|
FINISHED |
| Object | 551 |
—
|
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: 551 | Statement: [Atlas V 551, configurationNumber, 551]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationNumber Context triple: [Atlas V 551, configurationNumber, 551]
-
A.
modelNumber
chosen
Indicates that one entity is the specific model identifier or code assigned to another entity (such as a product or device).
-
B.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
C.
serviceNumbering
Indicates that a specific service is assigned or associated with a particular identifying number or code.
-
D.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
E.
hasPlatformNumber
Indicates that a location or service is associated with a specific platform identified by a platform number.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ab950d4819098d6a46f67c46191 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.