Triple
T32656979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson Muntz |
E834888
|
entity |
| Predicate | hasBrokenHomeBackground |
P181361
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nelson Muntz, hasBrokenHomeBackground, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrokenHomeBackground Context triple: [Nelson Muntz, hasBrokenHomeBackground, yes]
-
A.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
B.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
C.
hasNotableHostBackground
Indicates that the host of an event, show, or program has a background or profile that is considered particularly significant, distinguished, or noteworthy.
-
D.
hostBackground
Indicates that one entity serves as the environmental or contextual background in which another entity (typically a host or primary subject) is situated or presented.
-
E.
hasHomeFeature
Indicates that a home possesses or includes a particular feature or amenity.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: May 1, 2026, 1:08 a.m.