Triple
T5451418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterling area |
E122377
|
entity |
| Predicate | statusByLate20thCentury |
P17759
|
FINISHED |
| Object | largely dissolved |
—
|
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: largely dissolved | Statement: [Sterling area, statusByLate20thCentury, largely dissolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusByLate20thCentury Context triple: [Sterling area, statusByLate20thCentury, largely dissolved]
-
A.
statusIn20thCentury
chosen
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
B.
statusAsOf21stCentury
Indicates that the status or condition of an entity is evaluated or defined specifically as it stands in the 21st century.
-
C.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
D.
populationStatus19thCentury
Indicates the population condition or demographic status of an entity during the 19th century.
-
E.
statusAfter1923
Indicates the status or condition an entity has at some point after the year 1923.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.