Triple
T33758228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Community Church |
E865034
|
entity |
| Predicate | frequentAttendee |
P91340
|
FINISHED |
| Object | Ned Flanders |
—
|
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: Ned Flanders | Statement: [Springfield Community Church, frequentAttendee, Ned Flanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentAttendee Context triple: [Springfield Community Church, frequentAttendee, Ned Flanders]
-
A.
frequentPatron
chosen
Indicates that one entity regularly and repeatedly visits, uses, or patronizes another entity (such as a place, service, or establishment).
-
B.
frequentExhibitor
Indicates that an entity regularly or repeatedly participates as an exhibitor in events, shows, or exhibitions.
-
C.
frequentPartner
Indicates that two entities regularly engage in a shared activity or interaction together more often than with others.
-
D.
clubRegularAt
Indicates that an entity habitually and consistently frequents a particular club as a regular attendee.
-
E.
clubLoyalty
Indicates a sustained allegiance or commitment that an entity has toward a particular club or organization.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:45 a.m.