Triple
T26832247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbotsford Heat |
E675529
|
entity |
| Predicate | cityCouncilSubsidyInvolved |
P50645
|
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: [Abbotsford Heat, cityCouncilSubsidyInvolved, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCouncilSubsidyInvolved Context triple: [Abbotsford Heat, cityCouncilSubsidyInvolved, true]
-
A.
cityGovernmentSupport
chosen
Indicates that a city’s governing authorities provide backing, resources, or endorsement to a person, group, project, or initiative.
-
B.
cityCouncilApproved
Indicates that a city council has formally reviewed and granted approval for a proposed action, decision, or measure.
-
C.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
D.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
E.
districtContribution
Indicates that a specific district provides, allocates, or is responsible for a particular contribution (such as resources, funds, or support) toward a larger whole or initiative.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:02 a.m.