Triple
T29317170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canna House, Isle of Canna |
E743407
|
entity |
| Predicate | hasResearchAccess |
P201277
|
FINISHED |
| Object | by arrangement |
—
|
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: by arrangement | Statement: [Canna House, Isle of Canna, hasResearchAccess, by arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchAccess Context triple: [Canna House, Isle of Canna, hasResearchAccess, by arrangement]
-
A.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
B.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
C.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
D.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
-
E.
hasResearchFunction
Indicates that an entity possesses a role, capacity, or function specifically related to conducting or supporting research activities.
- F. None of above. chosen
Provenance (4 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: April 28, 2026, 1:20 p.m.