Triple
T38697639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Canadians |
E950046
|
entity |
| Predicate | notableAncestralRegion |
P164532
|
FINISHED |
| Object | Alps |
E16930
|
NE 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: Alps | Statement: [Swiss Canadians, notableAncestralRegion, Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAncestralRegion Context triple: [Swiss Canadians, notableAncestralRegion, Alps]
-
A.
notableFamilyOrigin
Indicates that an entity is recognized for originating from, or being notably associated with, a particular family background or lineage.
-
B.
partOfAncestralHomelandOf
Indicates that one entity constitutes a geographic or cultural portion of the ancestral homeland associated with another entity.
-
C.
recognizedAsAncestralNationOf
Indicates that one entity is formally acknowledged or regarded as the ancestral homeland or originating nation of another entity.
-
D.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
E.
mayIndicateAncestralOriginFrom
chosen
Indicates that one entity suggests or implies the ancestral origin or lineage of another entity.
- F. None of above.
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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f6f7e7c8190a655f8c77107d82a |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.