Triple
T3788549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Gorges Dam |
E89587
|
entity |
| Predicate | fullyOperationalDate |
P21563
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Three Gorges Dam, fullyOperationalDate, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyOperationalDate Context triple: [Three Gorges Dam, fullyOperationalDate, 2012]
-
A.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
B.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
C.
becameOperational
chosen
Indicates that an entity transitioned from a non-functioning or inactive state to an active, functioning, or service-ready state at a certain point in time.
-
D.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
E.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
- 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_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. |
Created at: March 9, 2026, 3:14 p.m.