Triple
T5661801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cades Cove |
E124758
|
entity |
| Predicate | firstEuropeanSettlersArrived |
P54294
|
FINISHED |
| Object | early 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: early 19th century | Statement: [Cades Cove, firstEuropeanSettlersArrived, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanSettlersArrived Context triple: [Cades Cove, firstEuropeanSettlersArrived, early 19th century]
-
A.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
-
B.
firstEuropeanSettlementOn
Indicates that one entity is the first European-established settlement located on the specified place or territory.
-
C.
firstPermanentEuropeanSettlement
chosen
Indicates that the subject is the location of the earliest lasting European-established community in a given region or context.
-
D.
yearOfArrivalInNewWorld
Indicates the specific year in which an entity arrived in the New World.
-
E.
firstContactWithEuropeans
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.