Triple
T21252678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poplar Hill First Nation |
E523783
|
entity |
| Predicate | serviceAccess |
P143389
|
FINISHED |
| Object | limited road access |
—
|
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: limited road access | Statement: [Poplar Hill First Nation, serviceAccess, limited road access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAccess Context triple: [Poplar Hill First Nation, serviceAccess, limited road access]
-
A.
serviceClassAccess
Indicates that one entity is permitted to use or interact with a particular class or category of service provided by another entity.
-
B.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
C.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
D.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
- F. None of above. chosen
Provenance (4 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359f5b408190b951adddba83c97a |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:57 p.m.