Triple
T25007071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Road |
E625870
|
entity |
| Predicate | hasFolkloricElements |
P120146
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The White Road, hasFolkloricElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFolkloricElements Context triple: [The White Road, hasFolkloricElements, true]
-
A.
includesFolklore
chosen
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
B.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
C.
usesFolkMaterial
Indicates that one entity incorporates or draws upon traditional folk materials, such as melodies, stories, or motifs, in relation to another entity.
-
D.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
E.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:05 a.m.