Triple
T32656971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nelson Muntz |
E834888
|
entity |
| Predicate | oftenSeenAt |
P91034
|
FINISHED |
| Object | Springfield Elementary playground |
—
|
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: Springfield Elementary playground | Statement: [Nelson Muntz, oftenSeenAt, Springfield Elementary playground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenSeenAt Context triple: [Nelson Muntz, oftenSeenAt, Springfield Elementary playground]
-
A.
oftenLocatedAt
chosen
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
bestSeenIn
Indicates that something is most effectively or appropriately experienced, observed, or appreciated within a particular context, medium, or setting.
-
C.
oftenLocatedAs
Indicates that one entity is frequently found or situated in the same place as another entity.
-
D.
isCommonlyFoundAt
Indicates that an entity typically or frequently occurs, appears, or is present in a particular location or context.
-
E.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:08 a.m.