Triple
T17063773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siler family |
E414028
|
entity |
| Predicate | timePeriodOfEarlySettlement |
P77757
|
FINISHED |
| Object | late 18th 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: late 18th century | Statement: [Siler family, timePeriodOfEarlySettlement, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfEarlySettlement Context triple: [Siler family, timePeriodOfEarlySettlement, late 18th century]
-
A.
earlierSettlementDate
Indicates that one settlement date occurs chronologically before another settlement date.
-
B.
earlierSettlement
Indicates that one settlement or agreement occurred or was reached before another in time.
-
C.
isEarlySettlementOf
Indicates that one settlement represents an earlier or initial phase, version, or establishment of another settlement.
-
D.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
E.
associatedSettlementPeriod
chosen
Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7f6a6081909bebce3ce925e663 |
completed | April 18, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.