Triple
T33108320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royaume d’Yvetot |
E847253
|
entity |
| Predicate | légendeAssociée |
P1582
|
FINISHED |
| Object | roi d’Yvetot tué par Clotaire Ier |
—
|
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: roi d’Yvetot tué par Clotaire Ier | Statement: [Royaume d’Yvetot, légendeAssociée, roi d’Yvetot tué par Clotaire Ier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: légendeAssociée Context triple: [Royaume d’Yvetot, légendeAssociée, roi d’Yvetot tué par Clotaire Ier]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
C.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
D.
featuredLegend
Indicates that an entity is highlighted or showcased as a prominent or notable legend within a given context.
-
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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e86f7c8190836278fd08e5cfed |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.