Triple
T30520410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durandal |
E776678
|
entity |
| Predicate | locationInLegend |
P25724
|
FINISHED |
| Object | Roncevaux Pass |
—
|
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: Roncevaux Pass | Statement: [Durandal, locationInLegend, Roncevaux Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInLegend Context triple: [Durandal, locationInLegend, Roncevaux Pass]
-
A.
legendLocation
chosen
Indicates the place or setting where a particular legend, myth, or traditional story is situated or associated.
-
B.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
C.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
D.
basedInLegend
Indicates that something is located, rooted, or primarily known within the context of a legend or mythic narrative.
-
E.
location depicted
Indicates that one entity visually represents or shows the place where another entity is situated or occurs.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: April 29, 2026, 8:17 p.m.