Triple
T12628831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apalachee people |
E301585
|
entity |
| Predicate | populationDeclineCentury |
P71532
|
FINISHED |
| Object | 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: 18th century | Statement: [Apalachee people, populationDeclineCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationDeclineCentury Context triple: [Apalachee people, populationDeclineCentury, 18th century]
-
A.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
-
B.
populationStatus19thCentury
Indicates the population condition or demographic status of an entity during the 19th century.
-
C.
populationLoss
chosen
Indicates a decrease in the number of individuals within a defined population over a given period or due to specific causes.
-
D.
disappearedByCentury
Indicates the century during which an entity ceased to exist, vanished, or was no longer present.
-
E.
historicalPeriodOfDecline
Indicates that an entity corresponds to a historical period characterized by decline or deterioration in another entity’s power, influence, stability, or prosperity.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.