Triple
T8183123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchmarnock |
E191115
|
entity |
| Predicate | hasHistoricRuins |
P33395
|
FINISHED |
| Object | medieval chapel ruins |
—
|
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: medieval chapel ruins | Statement: [Inchmarnock, hasHistoricRuins, medieval chapel ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRuins Context triple: [Inchmarnock, hasHistoricRuins, medieval chapel ruins]
-
A.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
B.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
C.
hasArchaeologicalFeature
chosen
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
D.
hasArchaeologicalRemainsFromPeriod
Indicates that an entity contains or preserves archaeological remains originating from a specified historical period.
-
E.
hasHistoricTownWallsRemnants
Indicates that remnants of historic town walls are present and associated with the subject entity.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4f4ef88190ad346edad14b67ee |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.