Triple
T32497703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South–North Water Transfer Project |
E830572
|
entity |
| Predicate | easternRouteOperationStart |
P174512
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [South–North Water Transfer Project, easternRouteOperationStart, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternRouteOperationStart Context triple: [South–North Water Transfer Project, easternRouteOperationStart, 2013]
-
A.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
startingGuardEast
Indicates that an entity begins in the role or position of a guard located on the east side or facing east.
-
C.
startingForwardEast
Indicates that an entity begins its movement or orientation facing toward the east direction.
-
D.
easternContinuationLeadsTo
Indicates that a path, route, or extension continues eastward from a given point and leads to another location or state.
-
E.
startingCenterEast
Indicates that an entity begins or is positioned at the central area of a region, oriented toward or located on the eastern side.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4409dc48190a9eac031b88571a1 |
completed | May 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:59 a.m.