Triple
T4146197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gezhouba Dam |
E89787
|
entity |
| Predicate | navigationFacility |
P25244
|
FINISHED |
| Object | ship lock complex |
—
|
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: ship lock complex | Statement: [Gezhouba Dam, navigationFacility, ship lock complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationFacility Context triple: [Gezhouba Dam, navigationFacility, ship lock complex]
-
A.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
transportationFacility
chosen
Indicates that one entity is a facility or location used for the transportation or transit of people or goods in relation to another entity.
-
D.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
E.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.