Triple
T3415402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelso Abbey |
E71995
|
entity |
| Predicate | onceRankedAs |
P29271
|
FINISHED |
| Object | one of the wealthiest monasteries in Scotland |
—
|
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: one of the wealthiest monasteries in Scotland | Statement: [Kelso Abbey, onceRankedAs, one of the wealthiest monasteries in Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onceRankedAs Context triple: [Kelso Abbey, onceRankedAs, one of the wealthiest monasteries in Scotland]
-
A.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
B.
rankedAmong
Indicates that an entity holds a specific position or status within a defined group, list, or hierarchy of comparable entities.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
formerRanking
chosen
Indicates that an entity previously held a particular rank or position but no longer does so.
-
E.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb929b8ec8190aef431ec8ea2cf80 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.