Triple
T42718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Quebec |
E840
|
entity |
| Predicate | historyPeriod |
P302
|
FINISHED |
| Object | post-Seven Years' War era |
—
|
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: post-Seven Years' War era | Statement: [Province of Quebec, historyPeriod, post-Seven Years' War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historyPeriod Context triple: [Province of Quebec, historyPeriod, post-Seven Years' War era]
-
A.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
D.
historicalOutcome
Indicates the result or consequence that an event, action, or situation produced in a historical context.
-
E.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24c083ad081909c1122c8fb29efdc |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24aba9a2c81909f769a8f22e30c92 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.