Triple
T4960247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilibino |
E111386
|
entity |
| Predicate | powerPlantCommissioningPeriod |
P17087
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Bilibino, powerPlantCommissioningPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerPlantCommissioningPeriod Context triple: [Bilibino, powerPlantCommissioningPeriod, 1970s]
-
A.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
B.
hydroelectricStationCommissioned
Indicates that a hydroelectric power station has been officially brought into operation or service on a specific date or in a specific context.
-
C.
powerplantLicenseBuiltAs
Indicates that a power plant has been constructed in accordance with, or as specified by, a particular license.
-
D.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
E.
commissionedDuring
chosen
Indicates that an entity was formally authorized, ordered, or initiated within a specified time period or event.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.