Triple
T33104745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Indiana |
E847155
|
entity |
| Predicate | earlyEuropeanClaimant |
P44834
|
FINISHED |
| Object | France |
—
|
NE NERFINISHED |
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: [History of Indiana, earlyEuropeanClaimant, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyEuropeanClaimant Context triple: [History of Indiana, earlyEuropeanClaimant, France]
-
A.
firstEuropeanClaimBy
Indicates that a place or territory was first formally claimed or asserted as possession by a specified European individual, group, or state.
-
B.
earlySettlers
Indicates that the associated entities were among the first people to inhabit or establish a community in a particular area.
-
C.
formerColonialClaimant
chosen
Indicates that one entity previously held, but no longer maintains, a colonial claim over another entity.
-
D.
firstContactWithEuropeans
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
E.
regionBeforeColonization
Indicates that a region is characterized or described as it existed prior to colonization by an external power.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.