Triple
T13245017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-119 |
E315377
|
entity |
| Predicate | nuclearReactorLocation |
P108721
|
FINISHED |
| Object | fuselage |
—
|
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: fuselage | Statement: [Tupolev Tu-119, nuclearReactorLocation, fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearReactorLocation Context triple: [Tupolev Tu-119, nuclearReactorLocation, fuselage]
-
A.
hasNuclearPowerPlantNearby
Indicates that an entity is located close to at least one nuclear power plant.
-
B.
powerplantLocation
Indicates that a power plant is situated at or associated with a specific geographic location.
-
C.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
D.
plutoniumFacility
Indicates a facility that is involved in the production, processing, handling, or storage of plutonium.
-
E.
nuclearPowerStationUnit
Indicates a relationship where an individual unit (such as a reactor or generating block) is part of or belongs to a specific nuclear power station.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5b06148190a44e698bbe5cd529 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:23 p.m.