Triple
T25807840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The North Bank Limited |
E650020
|
entity |
| Predicate | laterPowerType |
P175611
|
FINISHED |
| Object | diesel locomotive |
—
|
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: diesel locomotive | Statement: [The North Bank Limited, laterPowerType, diesel locomotive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPowerType Context triple: [The North Bank Limited, laterPowerType, diesel locomotive]
-
A.
previousPowerType
Indicates that one entity’s power type immediately preceded another entity’s power type in a sequence or history.
-
B.
laterPowerOutput
Indicates that the power output of an entity at a later time is being related or compared to its power output at an earlier time.
-
C.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
D.
laterPowerplant
Indicates that one power plant occurs, is built, or becomes operational at a later time than another power plant.
-
E.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 22, 2026, 7:05 a.m.