Triple
T11728231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wales Conference |
E278830
|
entity |
| Predicate | hadMemberTeamsFrom |
P33194
|
FINISHED |
| Object | Original Six franchises |
—
|
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: Original Six franchises | Statement: [Prince of Wales Conference, hadMemberTeamsFrom, Original Six franchises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMemberTeamsFrom Context triple: [Prince of Wales Conference, hadMemberTeamsFrom, Original Six franchises]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
memberTeamAtVariousTimes
Indicates that an entity has been a member of a particular team during one or more distinct time periods.
-
C.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
D.
hadTeamFromCountry
chosen
Indicates that an entity (such as an event, league, or competition) included or was associated with at least one team originating from a specified country.
-
E.
hasTeamMember
Indicates that an entity includes another entity as a member of its team.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.