Triple
T657462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchcolm |
E11678
|
entity |
| Predicate | hasArchaeologicalInterest |
P12027
|
FINISHED |
| Object | medieval remains |
—
|
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 remains | Statement: [Inchcolm, hasArchaeologicalInterest, medieval remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalInterest Context triple: [Inchcolm, hasArchaeologicalInterest, medieval remains]
-
A.
hasArchaeologicalValue
chosen
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
B.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
C.
hasArchitecturalSignificance
Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
-
D.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
E.
hasArtHistoricalSignificance
Indicates that something holds notable importance or influence within the context of art history.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa55e048190bd9913c6c31772d0 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.