Triple
T33678185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huron-Wendat Confederacy |
E862819
|
entity |
| Predicate | firstSustainedContactWith |
P10100
|
FINISHED |
| Object | France |
E861
|
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: France | Statement: [Huron-Wendat Confederacy, firstSustainedContactWith, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSustainedContactWith Context triple: [Huron-Wendat Confederacy, firstSustainedContactWith, France]
-
A.
firstContactWithHumans
Indicates that the subject entity is the first to establish contact or interaction with humans.
-
B.
firstContactWithEuropeans
chosen
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
C.
earlyUSContact
Indicates that there was contact or interaction between the entities during the early period of United States history.
-
D.
preColumbianContact
Indicates that there was interaction or contact between peoples or cultures before Columbus’s arrival in the Americas.
-
E.
firstMajorExplorationIn
Indicates that an entity represents the earliest significant exploration activity that took place in a specified location or context.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36271510a08190960b75f75ddd7f5b |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:43 a.m.