Triple
T8715949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culebra Cut |
E206893
|
entity |
| Predicate | excavationVolume |
P84057
|
FINISHED |
| Object | over 100 million cubic yards of material |
—
|
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: over 100 million cubic yards of material | Statement: [Culebra Cut, excavationVolume, over 100 million cubic yards of material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationVolume Context triple: [Culebra Cut, excavationVolume, over 100 million cubic yards of material]
-
A.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
-
B.
excavated
Indicates that one entity has dug out, uncovered, or removed earth or material from another entity, typically to reveal or extract what lies beneath.
-
C.
excavationStatus
Indicates the current state or phase of an excavation activity, such as whether it is planned, in progress, paused, or completed.
-
D.
excavationPurpose
Indicates that an excavation is carried out with a specific intended purpose or objective.
-
E.
excavationEnd
Indicates the point in time or event at which an excavation activity is completed or brought to an end.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd807cc819090b58caf285b397a |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:35 p.m.