Triple
T35427882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deserted Village at Slievemore |
E1023968
|
entity |
| Predicate | wasPrimarilyAbandonedInCentury |
P72776
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Deserted Village at Slievemore, wasPrimarilyAbandonedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPrimarilyAbandonedInCentury Context triple: [Deserted Village at Slievemore, wasPrimarilyAbandonedInCentury, 19th century]
-
A.
abandonedCentury
chosen
Indicates that something or someone ceased to be used, maintained, or inhabited during a particular century.
-
B.
abandonedAsCapitalInCentury
Indicates that a city or settlement ceased to function as a capital during the specified century.
-
C.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
-
D.
decommissionedInCentury
Indicates that something was formally taken out of service or use during a specified century.
-
E.
usedAsPrimarySettlementUntil
Indicates that an entity served as the main or principal settlement for another entity up to a specified point in time.
- 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.