Triple
T3788570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Gorges Dam |
E89587
|
entity |
| Predicate | hasShipLock |
P51758
|
FINISHED |
| Object | five-step ship lock |
—
|
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: five-step ship lock | Statement: [Three Gorges Dam, hasShipLock, five-step ship lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipLock Context triple: [Three Gorges Dam, hasShipLock, five-step ship lock]
-
A.
hasShip
Indicates that one entity possesses, owns, or is equipped with a ship.
-
B.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
C.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
D.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
-
E.
stateShip
Indicates that a ship is officially registered, documented, or associated with a particular state or governmental authority.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeecee63e8819099b8ee8ad4d4354e |
completed | March 9, 2026, 3:53 p.m. |
Created at: March 9, 2026, 3:14 p.m.