Triple
T31890019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All My Ex's Live in Texas |
E814121
|
entity |
| Predicate | hasPlaceReference |
P118404
|
FINISHED |
| Object | 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: Tennessee | Statement: [All My Ex's Live in Texas, hasPlaceReference, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceReference Context triple: [All My Ex's Live in Texas, hasPlaceReference, Tennessee]
-
A.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
B.
placeMentioned
chosen
Indicates that a specific place is referenced or mentioned in relation to another entity or context.
-
C.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
D.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
E.
hasPlaceNamesIn
Indicates that something contains, references, or is associated with one or more place names within it.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 30, 2026, 11:57 p.m.