Triple
T11302123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference |
E267619
|
entity |
| Predicate | conferenceSystem |
P47976
|
FINISHED |
| Object | two-conference league structure |
—
|
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: two-conference league structure | Statement: [Western Conference, conferenceSystem, two-conference league structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceSystem Context triple: [Western Conference, conferenceSystem, two-conference league structure]
-
A.
conferenceStructure
Indicates how a conference is organized into its constituent parts, such as sessions, tracks, and events, and the relationships among them.
-
B.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
C.
conferenceServed
Indicates that a particular conference provided services, resources, or support to a specified entity (such as attendees, organizations, or events).
-
D.
hasConferenceSystem
chosen
Indicates that an entity is equipped with or utilizes a particular conference or conferencing system.
-
E.
conferenceStatus
Indicates the current state or phase of a conference within its lifecycle (e.g., planned, active, completed, or canceled).
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a5c3788190ba54eda514b97903 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.