Triple
T33678186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huron-Wendat Confederacy |
E862819
|
entity |
| Predicate | timeOfMajorContact |
P132167
|
FINISHED |
| Object | early 17th century |
—
|
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: early 17th century | Statement: [Huron-Wendat Confederacy, timeOfMajorContact, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorContact Context triple: [Huron-Wendat Confederacy, timeOfMajorContact, early 17th century]
-
A.
timeOfNotableContact
chosen
Indicates the specific time at which a notable or significant contact or interaction between entities occurred.
-
B.
timeOfMajorStrike
Indicates the specific time at which a major strike or significant labor action occurs.
-
C.
historicalPeriodOfMajorContact
Indicates the historical time period during which the most significant or intensive contact occurred between the related entities.
-
D.
timeOfMajorBreakup
Indicates the specific time or period when a significant breakup or separation between the related entities occurred.
-
E.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:43 a.m.