Triple
T17650115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulkatcho First Nation |
E429464
|
entity |
| Predicate | peopleCountDate |
P111137
|
FINISHED |
| Object | around 2020 |
—
|
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: around 2020 | Statement: [Ulkatcho First Nation, peopleCountDate, around 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleCountDate Context triple: [Ulkatcho First Nation, peopleCountDate, around 2020]
-
A.
peopleCountDescriptor
Indicates how the number of people involved in a situation, group, or context is characterized or described.
-
B.
hasApproximateNumberOfPeople
chosen
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
C.
guestCountApproximate
Indicates that the number of guests involved is represented as an estimated or approximate count rather than an exact figure.
-
D.
numberOfPersons
Indicates the total count of individual persons associated with or involved in a given entity, event, or context.
-
E.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3c7da48190b38558bc66637687 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.