Triple
T27631501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan C |
E696347
|
entity |
| Predicate | depthOfRescueShaft |
P43725
|
FINISHED |
| Object | approximately 622 meters |
—
|
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 622 meters | Statement: [Plan C, depthOfRescueShaft, approximately 622 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthOfRescueShaft Context triple: [Plan C, depthOfRescueShaft, approximately 622 meters]
-
A.
hasCaveEntranceDepth
Indicates the depth or vertical distance of a cave’s entrance relative to a reference level (such as ground surface or sea level).
-
B.
hasEmergencyExitShafts
Indicates that an entity is equipped with one or more dedicated emergency exit shafts for evacuation or escape purposes.
-
C.
hasUndergroundDepth
chosen
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
D.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
E.
undergroundCavernWidth
Indicates the horizontal extent or span of an underground cavern from one side to the other.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63123c4808190b919dccfab60b582 |
completed | May 2, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:21 p.m.