Triple
T6990350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Inga Dam Project |
E162068
|
entity |
| Predicate | expectedToBe |
P32577
|
FINISHED |
| Object | world’s largest power station |
—
|
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: world’s largest power station | Statement: [Grand Inga Dam Project, expectedToBe, world’s largest power station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedToBe Context triple: [Grand Inga Dam Project, expectedToBe, world’s largest power station]
-
A.
isSupposedToBe
chosen
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
B.
setsExpectationsFor
Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
-
C.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
D.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
E.
containsProphecyAbout
Indicates that one entity includes or conveys a prediction or foretelling specifically concerning another entity.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc08758819083d36a1fc0463b27 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.