Triple
T27251471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Ninian's Isle treasure |
E687496
|
entity |
| Predicate | foundAtSiteType |
P53032
|
FINISHED |
| Object | church site |
—
|
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: church site | Statement: [St Ninian's Isle treasure, foundAtSiteType, church site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAtSiteType Context triple: [St Ninian's Isle treasure, foundAtSiteType, church site]
-
A.
hasFindingSite
Indicates that a particular finding, observation, or abnormality is located in or associated with a specific anatomical site.
-
B.
isTypeSiteOf
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
hasTypeSiteFor
Indicates that one entity serves as the specific site or location designated for a particular type or category of another entity.
-
E.
associatedSiteType
chosen
Indicates the type or category of site with which an entity is associated.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 10:45 a.m.