Triple
T35719712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan II |
E1032436
|
entity |
| Predicate | fuelStorageCapability |
P54417
|
FINISHED |
| Object | long-term storable |
—
|
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: long-term storable | Statement: [Titan II, fuelStorageCapability, long-term storable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelStorageCapability Context triple: [Titan II, fuelStorageCapability, long-term storable]
-
A.
hasFuelStorage
chosen
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
B.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
C.
fuelLocation
Indicates the place or source where fuel is stored, supplied, or located for use.
-
D.
fuelTankConfiguration
Indicates how a system’s fuel tanks are arranged, connected, or structured relative to one another.
-
E.
fuelCapacityPounds
Indicates the maximum amount of fuel an entity can hold, measured in pounds.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.