Triple
T15641265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indigenous peoples of Florida |
E376069
|
entity |
| Predicate | firstEuropeanContactPeriod |
P10100
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Indigenous peoples of Florida, firstEuropeanContactPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanContactPeriod Context triple: [Indigenous peoples of Florida, firstEuropeanContactPeriod, 16th century]
-
A.
firstContactWithEuropeans
chosen
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
B.
earlyUSContact
Indicates that there was contact or interaction between the entities during the early period of United States history.
-
C.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity took place.
-
D.
preColumbianContact
Indicates that there was interaction or contact between peoples or cultures before Columbus’s arrival in the Americas.
-
E.
dateOfFirstEuropeanLanding
Indicates the date on which Europeans first arrived at or made landfall on a particular 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed23d688190bea996f90989d406 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.