Triple
T28173683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davenport |
E715530
|
entity |
| Predicate | timeOfInitialEuropeanSettlement |
P80577
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Davenport, timeOfInitialEuropeanSettlement, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfInitialEuropeanSettlement Context triple: [Davenport, timeOfInitialEuropeanSettlement, 19th century]
-
A.
dateOfFirstEuropeanLanding
Indicates the date on which Europeans first arrived at or made landfall on a particular place.
-
B.
earliestEuropeanSettlementCentury
chosen
Indicates the century during which the earliest European settlement associated with the subject was established.
-
C.
colonizationStartYear
Indicates the year in which a process of colonization of a place or territory began.
-
D.
firstEuropeanSettlementOn
Indicates that one entity is the first European-established settlement located on the specified place or territory.
-
E.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 10:14 p.m.