Triple
T9681781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Touch |
E234297
|
entity |
| Predicate | labelTerritory |
P63197
|
FINISHED |
| Object | Nettwerk in Canada |
—
|
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: Nettwerk in Canada | Statement: [Touch, labelTerritory, Nettwerk in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelTerritory Context triple: [Touch, labelTerritory, Nettwerk in Canada]
-
A.
associatedTitleTerritory
Indicates a relationship where a specific title is linked or connected to a particular territory or domain.
-
B.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
E.
labelRegion
chosen
Indicates assigning a categorical or descriptive label to a specified region or area.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9fec1c8190b2626848cb2c1871 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.