Triple
T20871397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montagnais |
E513900
|
entity |
| Predicate | historicallyCalledBy |
P2834
|
FINISHED |
| Object | French colonists |
—
|
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: French colonists | Statement: [Montagnais, historicallyCalledBy, French colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyCalledBy Context triple: [Montagnais, historicallyCalledBy, French colonists]
-
A.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
-
B.
historicallyBorneBy
chosen
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
C.
historicallyImplementedAs
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
D.
isHistoricallyDependentOn
Indicates that one entity’s existence, development, or validity is contingent on prior events, conditions, or states associated with another entity in history.
-
E.
historicallyGivenTo
Indicates that something was transferred or bestowed upon an entity at some point in the past, typically as recorded or recognized in historical accounts.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4649cf88190b3ad946576aa46aa |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.