Triple
T17466786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunavut Act |
E425296
|
entity |
| Predicate | dateTerritoryCreated |
P105537
|
FINISHED |
| Object | 1999-04-01 |
—
|
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: 1999-04-01 | Statement: [Nunavut Act, dateTerritoryCreated, 1999-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateTerritoryCreated Context triple: [Nunavut Act, dateTerritoryCreated, 1999-04-01]
-
A.
relatedTerritoryCreationDate
chosen
Indicates the date on which the associated or linked territory was officially created or established.
-
B.
dateTerritoryReduced
Indicates the date on which a territory’s size, control, or jurisdiction was officially reduced.
-
C.
registeredAt
Indicates that an entity has officially enrolled, signed up, or been recorded in a system, organization, or event at a specific place or time.
-
D.
dateOfCreationAsSeparateRealm
Indicates the point in time when something was first established or recognized as an independent, distinct realm or domain.
-
E.
createdAtOrganization
Indicates the time or context in which something was created while associated with a particular organization.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a7e2a481908c32defa3401f848 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.