Triple
T8170266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Water Line |
E190797
|
entity |
| Predicate | tooDeepFor |
P81075
|
FINISHED |
| Object | passage by infantry and cavalry |
—
|
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: passage by infantry and cavalry | Statement: [Dutch Water Line, tooDeepFor, passage by infantry and cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tooDeepFor Context triple: [Dutch Water Line, tooDeepFor, passage by infantry and cavalry]
-
A.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
B.
reachedDepth
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
C.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
D.
isDeeperThan
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
E.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4803de688190960438aa059d163b |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb40a017608190b6b48cf60335fa8d |
completed | March 31, 2026, 3:33 a.m. |
Created at: March 30, 2026, 5:39 p.m.