Triple
T10403180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Ursula |
E245197
|
entity |
| Predicate | legendIncludes |
P89511
|
FINISHED |
| Object | voyage by sea to join her betrothed |
—
|
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: voyage by sea to join her betrothed | Statement: [Saint Ursula, legendIncludes, voyage by sea to join her betrothed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legendIncludes Context triple: [Saint Ursula, legendIncludes, voyage by sea to join her betrothed]
-
A.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
B.
legendDetail
chosen
Indicates that additional explanatory or descriptive information is provided about a legend or key associated with another element.
-
C.
includedOnLabel
Indicates that something is printed, listed, or otherwise shown on a label.
-
D.
legendLocation
Indicates the place or setting where a particular legend, myth, or traditional story is situated or associated.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e535d48190b8fc377df543e058 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:08 p.m.