Triple
T36568785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon Legislative Assembly |
E902055
|
entity |
| Predicate | hasHouseLeaderTitle |
P97730
|
FINISHED |
| Object | Government House Leader |
—
|
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: Government House Leader | Statement: [Yukon Legislative Assembly, hasHouseLeaderTitle, Government House Leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseLeaderTitle Context triple: [Yukon Legislative Assembly, hasHouseLeaderTitle, Government House Leader]
-
A.
hasStateLeaderTitle
Indicates the official title held by the leader of a state.
-
B.
hasCollectiveLeaderTitle
chosen
Indicates that a collective entity (such as a group, organization, or body) holds or is associated with a specific leadership title.
-
C.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
D.
hasChiefTitle
Indicates that an entity holds or is associated with a specific chief-level title or designation within an organization or group.
-
E.
hasLegislativeBodyTitle
Indicates the official title or designation used for the legislative body associated with an entity.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:11 p.m.