Triple
T18196989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference (WHL) |
E435685
|
entity |
| Predicate | conferenceOf |
P3308
|
FINISHED |
| Object | WHL Eastern teams |
—
|
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: WHL Eastern teams | Statement: [Eastern Conference (WHL), conferenceOf, WHL Eastern teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceOf Context triple: [Eastern Conference (WHL), conferenceOf, WHL Eastern teams]
-
A.
conference
Indicates that an entity organizes, hosts, or is associated with a formal meeting or event where participants gather to discuss specific topics or share information.
-
B.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
-
C.
conference2
chosen
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
D.
otherConference
Indicates that one conference is distinct from and not the same as another conference.
-
E.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d377d48190869a033d12f6ee80 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.