Triple
T8715901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaillard Cut |
E206892
|
entity |
| Predicate | maximumDepthExcavation |
P43725
|
FINISHED |
| Object | over 100 meters in some sections |
—
|
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 meters in some sections | Statement: [Gaillard Cut, maximumDepthExcavation, over 100 meters in some sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDepthExcavation Context triple: [Gaillard Cut, maximumDepthExcavation, over 100 meters in some sections]
-
A.
maximumDiveDepth
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
B.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
-
C.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
D.
hasUndergroundDepth
chosen
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
E.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
- 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_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. |
Created at: March 30, 2026, 6:35 p.m.