Triple
T21064192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAU-68 |
E518924
|
entity |
| Predicate | tubeConfiguration |
P36973
|
FINISHED |
| Object | 7-tube launcher |
—
|
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: 7-tube launcher | Statement: [LAU-68, tubeConfiguration, 7-tube launcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tubeConfiguration Context triple: [LAU-68, tubeConfiguration, 7-tube launcher]
-
A.
tierConfiguration
Indicates how entities are organized or assigned into different levels or tiers according to a defined configuration or scheme.
-
B.
hasTube
chosen
Indicates that one entity possesses, includes, or is equipped with a tube as a component or feature.
-
C.
thirdTubeOpened
Indicates that the third tube in a set or sequence has been opened.
-
D.
nozzleConfiguration
Indicates the specific arrangement or setup of nozzles used in a system or device.
-
E.
stageConfiguration
Indicates the specific arrangement or setup of components, elements, or conditions at a particular stage within a process or system.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb29e388190a80fa969a4daa606 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:43 p.m.