Triple
T28737607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of North Vancouver Council |
E730843
|
entity |
| Predicate | hasMayorAsChair |
P105645
|
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: [District of North Vancouver Council, hasMayorAsChair, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMayorAsChair Context triple: [District of North Vancouver Council, hasMayorAsChair, true]
-
A.
hasBoardChairperson
Indicates that an entity has a specific person serving as the chairperson of its board.
-
B.
hasCoChair
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
-
C.
hasChairHolder
chosen
Indicates that an entity holds or occupies a specific chair position or role associated with another entity.
-
D.
hasCoChairSystem
Indicates that an entity is associated with or governed by a system in which responsibilities or roles are jointly shared by co-chairs.
-
E.
hasChairpersonOrgan
Indicates that an organization or body has a specific organ (such as a board or committee) that holds the role of chairperson.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 28, 2026, 6:01 a.m.