Triple
T24924412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timiskaming First Nation |
E618810
|
entity |
| Predicate | hasDistinctGovernance |
P118045
|
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: [Timiskaming First Nation, hasDistinctGovernance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctGovernance Context triple: [Timiskaming First Nation, hasDistinctGovernance, true]
-
A.
governanceDiffersFrom
Indicates that the form, structure, or style of governance of one entity is different from that of another entity.
-
B.
hasPrimaryGovernance
Indicates that one entity holds the main authority or responsibility for directing, controlling, or overseeing the governance of another entity or domain.
-
C.
hasGovernanceLevel
Indicates the degree or tier of authority, control, or decision-making power that an entity holds within a governance structure.
-
D.
hasGovernanceForm
chosen
Indicates that an entity is organized or administered according to a particular system or form of governance.
-
E.
hasGoverness
Indicates that one entity is served or cared for by another entity in the role of a governess.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 5:29 a.m.