Triple
T15090413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Lochbuie |
E360398
|
entity |
| Predicate | recognizedWithin |
P4733
|
FINISHED |
| Object | Scottish heraldic tradition |
—
|
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 heraldic tradition | Statement: [Maclean of Lochbuie, recognizedWithin, Scottish heraldic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedWithin Context triple: [Maclean of Lochbuie, recognizedWithin, Scottish heraldic tradition]
-
A.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
-
B.
recognizedIn
chosen
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
C.
recognizedOn
Indicates that an entity was formally acknowledged, identified, or honored on a specific date or occasion.
-
D.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
-
E.
recognizedThrough
Indicates that something becomes known, identified, or acknowledged by means of a particular method, medium, or process.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.