Triple
T1189019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Joint Commission |
E25314
|
entity |
| Predicate | hasCanadianCommissioners |
P21525
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [International Joint Commission, hasCanadianCommissioners, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanadianCommissioners Context triple: [International Joint Commission, hasCanadianCommissioners, 3]
-
A.
numberOfCommissioners
chosen
Indicates the specific count of commissioners associated with a given entity or context.
-
B.
hasRegionalCommission
Indicates that an entity is associated with, overseen by, or falls under the jurisdiction of a specific regional commission.
-
C.
hasCountyCommissioners
Indicates that an entity is governed or overseen by one or more county commissioners.
-
D.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
E.
allowsNHLAssignments
Indicates that one party permits or authorizes the assignment or transfer of rights, responsibilities, or personnel related to the NHL to another party.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd57c3c481908bdca483fcaa3297 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.