Triple
T32593472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ste. Geneviève |
E833132
|
entity |
| Predicate | hasHistoricPopulationOrigin |
P1823
|
FINISHED |
| Object | French settlers |
—
|
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 settlers | Statement: [Ste. Geneviève, hasHistoricPopulationOrigin, French settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricPopulationOrigin Context triple: [Ste. Geneviève, hasHistoricPopulationOrigin, French settlers]
-
A.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
B.
haveHistoricalMigrationWavesSince
Indicates that there have been one or more significant migration waves involving the subject entity starting from a specified historical time onward.
-
C.
hasHistoricalOriginInYear
Indicates that something first originated, began, or came into existence in a specified calendar year.
-
D.
hasLocalHistoricalRoots
Indicates that something originates from, or is significantly shaped by, the history and traditions of a particular local area.
-
E.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 1, 2026, 1:05 a.m.