Triple
T6941764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverbervie |
E160691
|
entity |
| Predicate | hasLocalMuseumOrHeritageCentre |
P37091
|
FINISHED |
| Object | Bervie Heritage group displays |
—
|
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: Bervie Heritage group displays | Statement: [Inverbervie, hasLocalMuseumOrHeritageCentre, Bervie Heritage group displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalMuseumOrHeritageCentre Context triple: [Inverbervie, hasLocalMuseumOrHeritageCentre, Bervie Heritage group displays]
-
A.
hasMuseumAt
chosen
Indicates that a museum is located at or exists in a specified place or location.
-
B.
hasNumberOfMuseums
Indicates the quantity of museums associated with a given entity.
-
C.
hasMemorialMuseum
Indicates that a memorial museum is dedicated to, associated with, or established in honor of a particular entity.
-
D.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
-
E.
hasArchaeologicalMuseum
Indicates that an entity possesses or hosts an archaeological museum as part of its features or facilities.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.