Triple
T12579408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunavut Land Claims Agreement |
E300294
|
entity |
| Predicate | relatedTerritoryCreationDate |
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 Land Claims Agreement, relatedTerritoryCreationDate, 1999-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTerritoryCreationDate Context triple: [Nunavut Land Claims Agreement, relatedTerritoryCreationDate, 1999-04-01]
-
A.
relatedTerritory
Indicates that one territory has a specified relationship or association with another territory.
-
B.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
-
C.
associatedTitleTerritory
Indicates a relationship where a specific title is linked or connected to a particular territory or domain.
-
D.
countryVariant
Indicates that one entity is a country-specific variant or localized version of another entity.
-
E.
availableNationwideSince
Indicates the date or time from which something has been available or offered across an entire nation.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5 p.m.