Triple
T31458629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clanranald |
E802524
|
entity |
| Predicate | clanPipeTune |
P163486
|
FINISHED |
| Object | Thogail nam Bò (The Cattle Lifting) |
—
|
NE NERFINISHED |
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: Thogail nam Bò (The Cattle Lifting) | Statement: [Clanranald, clanPipeTune, Thogail nam Bò (The Cattle Lifting)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanPipeTune Context triple: [Clanranald, clanPipeTune, Thogail nam Bò (The Cattle Lifting)]
-
A.
hasPipesAndDrums
chosen
Indicates that an entity possesses or is associated with a pipes and drums musical unit or ensemble.
-
B.
hasPipeOrgan
Indicates that one entity possesses, contains, or is equipped with a pipe organ.
-
C.
numberOfOrganPipes
Indicates the quantitative relationship specifying how many organ pipes are associated with a given organ or organ-related entity.
-
D.
pipeType
Indicates the specific kind or category of pipe associated with or used in relation to an entity.
-
E.
tuningDivision
Indicates a relationship where one entity specifies or defines the division or partitioning scheme used to tune or configure another entity.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:18 p.m.