Triple
T35263557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Day You'll Be Mine |
E1018437
|
entity |
| Predicate | performerRaisedIn |
P198559
|
FINISHED |
| Object | Chattanooga, Tennessee |
E791679
|
NE 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: Chattanooga, Tennessee | Statement: [One Day You'll Be Mine, performerRaisedIn, Chattanooga, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerRaisedIn Context triple: [One Day You'll Be Mine, performerRaisedIn, Chattanooga, Tennessee]
-
A.
performerOrigin
Indicates that a performer originates from, or is associated with, a particular place or region.
-
B.
hasPerformerBirthCity
Indicates the city in which the performer was born.
-
C.
performerBirthName
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
-
D.
performerLaterNationality
Indicates that the performer acquired or held this nationality at a later point in their life, after an earlier or original nationality.
-
E.
hasPerformerResidence
Indicates that a performer is associated with a particular place as their residence.
- F. None of above. chosen
Provenance (5 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a17a34c8190915cf4f0778d6a7d |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
| PDg | Predicate description generation | batch_69fef2da7d388190a5712a5094741f18 |
completed | May 9, 2026, 8:39 a.m. |
Created at: May 3, 2026, 4:02 p.m.