Triple
T12167086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingleville, Texas |
E289860
|
entity |
| Predicate | populationTrend20thCentury |
P67966
|
FINISHED |
| Object | declining |
—
|
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: declining | Statement: [Lingleville, Texas, populationTrend20thCentury, declining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationTrend20thCentury Context triple: [Lingleville, Texas, populationTrend20thCentury, declining]
-
A.
populationStatus19thCentury
Indicates the population condition or demographic status of an entity during the 19th century.
-
B.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
C.
centuryOfMajorMigration
Indicates the century during which a major migration event involving the entity took place.
-
D.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
E.
historicalPopulationCharacteristic
chosen
Indicates a relationship where an entity is associated with a demographic or population-related attribute that held true during a specific historical period.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.