Triple
T35427883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deserted Village at Slievemore |
E1023968
|
entity |
| Predicate | furtherDepopulatedInCentury |
P154146
|
FINISHED |
| Object | early 20th 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 20th century | Statement: [Deserted Village at Slievemore, furtherDepopulatedInCentury, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherDepopulatedInCentury Context triple: [Deserted Village at Slievemore, furtherDepopulatedInCentury, early 20th century]
-
A.
disappearedByCentury
Indicates the century during which an entity ceased to exist, vanished, or was no longer present.
-
B.
wasRepopulatedInCentury
Indicates that a place or region, previously depopulated or abandoned, became populated again during the specified century.
-
C.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
D.
depopulatedDuring
chosen
Indicates that a place lost most or all of its population during a specified time period or event.
-
E.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795940a48819095fd80a2e25946f7 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.