Triple
T33103494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelbyville |
E847122
|
entity |
| Predicate | relationshipToSpringfield |
P206350
|
FINISHED |
| Object | rival town |
—
|
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: rival town | Statement: [Shelbyville, relationshipToSpringfield, rival town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSpringfield Context triple: [Shelbyville, relationshipToSpringfield, rival town]
-
A.
relationshipToPawneeNation
Indicates the specific type of familial, legal, historical, or political relationship that an entity has with the Pawnee Nation.
-
B.
relationshipToHomer
Indicates the specific familial or social relationship that one entity has to Homer.
-
C.
relationshipToWalterSobchak
Indicates the specific personal or social relationship that one entity has to Walter Sobchak.
-
D.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
E.
relationshipToFerris
Indicates the specific familial, social, or professional relationship that one entity has to Ferris.
- F. None of above. chosen
Provenance (4 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:26 a.m.