Triple
T26451065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slioch |
E665347
|
entity |
| Predicate | hasGaelicNameVariant |
P8668
|
FINISHED |
| Object | Sliabhach (sometimes cited in older sources) |
—
|
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: Sliabhach (sometimes cited in older sources) | Statement: [Slioch, hasGaelicNameVariant, Sliabhach (sometimes cited in older sources)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGaelicNameVariant Context triple: [Slioch, hasGaelicNameVariant, Sliabhach (sometimes cited in older sources)]
-
A.
hasGaelicNameMeaning
Indicates that an entity’s Gaelic name carries a specific meaning or translation.
-
B.
GaelicName
chosen
Indicates that an entity has a name expressed in the Gaelic language.
-
C.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
D.
equivalentNameInScottishGaelic
Indicates that one entity’s name is the equivalent form of another entity’s name specifically in Scottish Gaelic.
-
E.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:05 a.m.