Triple
T36903092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Valley Authority Norris Dam project |
E912091
|
entity |
| Predicate | createdTown |
P115568
|
FINISHED |
| Object | Norris, Tennessee |
—
|
NE NERFINISHED |
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: Norris, Tennessee | Statement: [Tennessee Valley Authority Norris Dam project, createdTown, Norris, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdTown Context triple: [Tennessee Valley Authority Norris Dam project, createdTown, Norris, Tennessee]
-
A.
fromTown
Indicates that one entity originates from, or is associated as being from, a particular town represented by the other entity.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
createdCivilDivision
Indicates that one entity brought a civil administrative division (such as a district, county, or municipality) into existence or formally established it.
-
D.
developedAsNewTown
chosen
Indicates that a settlement or urban area was intentionally planned and constructed as a new town, rather than evolving organically from an existing settlement.
-
E.
isPlannedTown
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
- 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_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.