Triple
T18014005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu Gorge |
E430954
|
entity |
| Predicate | sequencePositionInThreeGorges |
P86484
|
FINISHED |
| Object | middle gorge |
—
|
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: middle gorge | Statement: [Wu Gorge, sequencePositionInThreeGorges, middle gorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequencePositionInThreeGorges Context triple: [Wu Gorge, sequencePositionInThreeGorges, middle gorge]
-
A.
segmentPositioning
Indicates how segments are arranged or ordered relative to one another within a larger structure or sequence.
-
B.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
C.
segmentPosition
chosen
Indicates the relative location or ordering of a segment within a larger sequence or structure.
-
D.
segmentLocation
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
E.
positionInCanal
Indicates that an entity occupies a specific location within a canal.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b521befc81908dff44f19aa3d580 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.