Triple
T35318358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meade Stadium |
E1019966
|
entity |
| Predicate | formerConferenceUse |
P21474
|
FINISHED |
| Object | Yankee Conference |
—
|
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: Yankee Conference | Statement: [Meade Stadium, formerConferenceUse, Yankee Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerConferenceUse Context triple: [Meade Stadium, formerConferenceUse, Yankee Conference]
-
A.
previousConferenceUse
Indicates that something has been used in a prior conference or earlier conference-related context.
-
B.
usedInConference
Indicates that something (such as a method, tool, or material) is employed or applied within the context of a particular conference.
-
C.
previouslyConveneAt
Indicates that an entity held or participated in a gathering, meeting, or session at a specified location or venue at some earlier time.
-
D.
previousConferenceHosted
Indicates that a specified entity hosted the immediately preceding instance of a particular conference.
-
E.
previousConferenceMembership
chosen
Indicates that an entity held membership in a conference or committee during a prior term or earlier time period.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:03 p.m.