Triple
T35818302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smokies Park |
E1035428
|
entity |
| Predicate | previousHomeOf |
P18609
|
FINISHED |
| Object | Knoxville Smokies |
—
|
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: Knoxville Smokies | Statement: [Smokies Park, previousHomeOf, Knoxville Smokies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomeOf Context triple: [Smokies Park, previousHomeOf, Knoxville Smokies]
-
A.
previousHome
chosen
Indicates that one entity served as a former or prior residence or home of another entity.
-
B.
previousLocationName
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
-
C.
previousTypicalLocation
Indicates that an entity was most commonly or characteristically located at a particular place in the past, before its current or later typical location.
-
D.
previousPeg
Indicates that one peg directly precedes another peg in a defined sequence or ordering.
-
E.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:06 p.m.