Triple
T34803440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHL regular season |
E1003280
|
entity |
| Predicate | usesConferences |
P178306
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [OHL regular season, usesConferences, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConferences Context triple: [OHL regular season, usesConferences, true]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
includeConferences
Indicates that certain conferences are to be contained within, or added as part of, a specified collection, context, or result set.
-
C.
conferencesInvolved
chosen
Indicates that an entity participates in, is associated with, or plays a role in one or more conferences.
-
D.
conferencesCovered
Indicates that one entity has reported on, documented, or provided coverage of one or more conferences associated with another entity.
-
E.
hasConferenceType
Indicates that an entity is associated with or classified by a specific type or category of conference.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 3:59 p.m.