Triple
T286329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Reactor |
E5892
|
entity |
| Predicate | shutdownDate |
P6603
|
FINISHED |
| Object | 1968-02-12 |
—
|
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: 1968-02-12 | Statement: [B Reactor, shutdownDate, 1968-02-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shutdownDate Context triple: [B Reactor, shutdownDate, 1968-02-12]
-
A.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
D.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
E.
closed
Indicates that an entity has brought something (such as an object, container, or space) from an open state into a shut or sealed state, or that it is currently in that shut state.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.