Triple
T27631500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan C |
E696347
|
entity |
| Predicate | timeToDrillRescueShaft |
P162779
|
FINISHED |
| Object | approximately 33 days |
—
|
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 33 days | Statement: [Plan C, timeToDrillRescueShaft, approximately 33 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToDrillRescueShaft Context triple: [Plan C, timeToDrillRescueShaft, approximately 33 days]
-
A.
timeInBunker
Indicates the duration that an entity spends inside a bunker.
-
B.
hasEmergencyExitShafts
Indicates that an entity is equipped with one or more dedicated emergency exit shafts for evacuation or escape purposes.
-
C.
tunnelDugBy
Indicates that a tunnel was created or excavated by a particular agent or entity.
-
D.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
E.
timeInTomb
Indicates the duration that an entity remains or has remained inside a tomb.
- 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_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. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:21 p.m.