Triple
T23365099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras Atomic Power Station |
E593293
|
entity |
| Predicate | commissionedUnit1 |
P52113
|
FINISHED |
| Object | 1984 |
—
|
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: 1984 | Statement: [Madras Atomic Power Station, commissionedUnit1, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedUnit1 Context triple: [Madras Atomic Power Station, commissionedUnit1, 1984]
-
A.
commissionedUnit
Indicates that one entity formally authorizes or assigns another entity (the commissioned unit) to carry out a specific task, role, or function.
-
B.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
C.
unit2Commissioned
chosen
Indicates that a second unit has been formally placed into active service or operation.
-
D.
commissionedWith
Indicates that one entity was created, produced, or initiated as part of the same commissioning event or request as another entity.
-
E.
commissioned
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.