Triple
T1656537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayton, Tennessee |
E35811
|
entity |
| Predicate | Rhea County Courthouse |
P7595
|
FINISHED |
| Object | site of the 1925 Scopes Trial |
—
|
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: site of the 1925 Scopes Trial | Statement: [Dayton, Tennessee, Rhea County Courthouse, site of the 1925 Scopes Trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Rhea County Courthouse Context triple: [Dayton, Tennessee, Rhea County Courthouse, site of the 1925 Scopes Trial]
-
A.
garrisonCounty
Indicates that a military garrison is stationed in, or assigned responsibility for, a particular county.
-
B.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
C.
hasCourthouse
chosen
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
D.
cityHallOf
Indicates that one entity serves as the official city hall building or administrative center for the specified city.
-
E.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.