Triple
T36903084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Valley Authority Norris Dam project |
E912091
|
entity |
| Predicate | damClosureDate |
P92642
|
FINISHED |
| Object | March 1936 |
—
|
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: March 1936 | Statement: [Tennessee Valley Authority Norris Dam project, damClosureDate, March 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damClosureDate Context triple: [Tennessee Valley Authority Norris Dam project, damClosureDate, March 1936]
-
A.
permanentClosureAnnouncementDate
Indicates the date on which an official announcement was made that something (such as a facility, service, or location) will be permanently closed.
-
B.
damRemovalCompletionDate
Indicates the date on which the removal of a dam is fully completed.
-
C.
closedOnDate
Indicates that an entity ceases or ceased operations or availability on a specific calendar date.
-
D.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
E.
finalShutdownDate
chosen
Indicates the date on which an entity is permanently shut down or ceases operation.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fda79b4c8190927740258cd7388b |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.