Triple
T34697840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okefenokee Oar |
E891078
|
entity |
| Predicate | usedInConference |
P197780
|
FINISHED |
| Object | Southeastern 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: Southeastern Conference | Statement: [Okefenokee Oar, usedInConference, Southeastern Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInConference Context triple: [Okefenokee Oar, usedInConference, Southeastern Conference]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
previousConferenceUse
Indicates that something has been used in a prior conference or earlier conference-related context.
-
C.
hadConference
Indicates that a conference event took place involving the specified entities (such as participants, organizations, or locations).
-
D.
usesConferenceStructure
Indicates that one entity organizes, presents, or operates another entity according to a conference-style structure or format.
-
E.
usesConferenceAlignment
Indicates that one entity organizes or structures something according to the conference-based alignment or grouping defined by another entity.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69feaa477f7c81909382b3aa77e7e11c |
completed | May 9, 2026, 3:30 a.m. |
Created at: May 1, 2026, 2:05 a.m.