Triple
T5579595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunessan |
E146607
|
entity |
| Predicate | hasBayNameEtymology |
P64557
|
FINISHED |
| Object | derived from Gaelic place-name "Bun Easain" |
—
|
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: derived from Gaelic place-name "Bun Easain" | Statement: [Bunessan, hasBayNameEtymology, derived from Gaelic place-name "Bun Easain"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayNameEtymology Context triple: [Bunessan, hasBayNameEtymology, derived from Gaelic place-name "Bun Easain"]
-
A.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
B.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
C.
seaNameEtymology
Indicates the origin or derivation of the name given to a particular sea.
-
D.
hasTitleEtymology
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
-
E.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0206bfea08190aa2c8df9f88013ac |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:37 p.m.