Triple
T35862734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional districts of British Columbia |
E1036996
|
entity |
| Predicate | includeEntityType |
P61589
|
FINISHED |
| Object | municipalities |
—
|
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: municipalities | Statement: [Regional districts of British Columbia, includeEntityType, municipalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeEntityType Context triple: [Regional districts of British Columbia, includeEntityType, municipalities]
-
A.
includedEntityType
chosen
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
B.
supportsEntityType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of entity.
-
C.
identifiesEntityType
Indicates that one entity specifies or determines the type or category to which another entity belongs.
-
D.
regulatesEntityType
Indicates that one entity exercises control, influence, or governance over the behavior, function, or state of another entity type.
-
E.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.