Triple
T34516500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiltartan |
E886164
|
entity |
| Predicate | hasFolkloreType |
P195734
|
FINISHED |
| Object | fairy lore |
—
|
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: fairy lore | Statement: [Kiltartan, hasFolkloreType, fairy lore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFolkloreType Context triple: [Kiltartan, hasFolkloreType, fairy lore]
-
A.
hasFolkTaleType
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
B.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
C.
includesFolklore
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
D.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
E.
folkloreFunction
Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 1, 2026, 2:01 a.m.