Triple
T30131526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Forest |
E765857
|
entity |
| Predicate | distanceFromChernobylNPP |
P202971
|
FINISHED |
| Object | approximately 1–2 kilometers west |
—
|
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: approximately 1–2 kilometers west | Statement: [Red Forest, distanceFromChernobylNPP, approximately 1–2 kilometers west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromChernobylNPP Context triple: [Red Forest, distanceFromChernobylNPP, approximately 1–2 kilometers west]
-
A.
distanceFromChernobylTown
Indicates the spatial distance between an entity and the town of Chernobyl.
-
B.
hasNuclearPowerPlantNearby
Indicates that an entity is located close to at least one nuclear power plant.
-
C.
distanceFromNearestSettlementKilometers
Indicates the distance, measured in kilometers, from an entity’s location to the closest human settlement.
-
D.
distanceFromKyiv
Indicates the spatial distance between a given entity’s location and the city of Kyiv.
-
E.
distanceFromHiroshimaCityCenter
Indicates the measured distance between a given location and the central point of Hiroshima City.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a00d76bde6c81909e564ab9cb0325af |
completed | May 10, 2026, 7:07 p.m. |
Created at: April 29, 2026, 7:15 p.m.