Triple
T37285686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Beggar Maid |
E925527
|
entity |
| Predicate | appearsInLegendWith |
P1582
|
FINISHED |
| Object | King Cophetua |
—
|
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: King Cophetua | Statement: [the Beggar Maid, appearsInLegendWith, King Cophetua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInLegendWith Context triple: [the Beggar Maid, appearsInLegendWith, King Cophetua]
-
A.
basedInLegend
Indicates that something is located, rooted, or primarily known within the context of a legend or mythic narrative.
-
B.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
E.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:16 p.m.