Triple
T27278474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchaffray Abbey |
E688262
|
entity |
| Predicate | grantedChartersBy |
P168079
|
FINISHED |
| Object | Scottish nobility |
—
|
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: Scottish nobility | Statement: [Inchaffray Abbey, grantedChartersBy, Scottish nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedChartersBy Context triple: [Inchaffray Abbey, grantedChartersBy, Scottish nobility]
-
A.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
B.
chartersTo
Indicates that one entity formally grants another entity the right to use or operate something (such as a vehicle, vessel, or service) under a charter agreement.
-
C.
grantedLettersOfMarqueBy
Indicates that one entity has been officially authorized by another entity, through letters of marque, to conduct privateering or similar sanctioned actions.
-
D.
landGrantedBy
Indicates that one party has given or transferred legal rights to a piece of land to another party.
-
E.
hasRoyalCharter
Indicates that an entity has been formally granted a royal charter by a monarch or royal authority.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 11:05 a.m.