Triple
T19237984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Sarah |
E481051
|
entity |
| Predicate | legendRole |
P134527
|
FINISHED |
| Object | servant of the Three Marys |
—
|
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: servant of the Three Marys | Statement: [Saint Sarah, legendRole, servant of the Three Marys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legendRole Context triple: [Saint Sarah, legendRole, servant of the Three Marys]
-
A.
inLegendRole
chosen
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
B.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
C.
legendStatus
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
D.
legendDetail
Indicates that additional explanatory or descriptive information is provided about a legend or key associated with another element.
-
E.
legendLocation
Indicates the place or setting where a particular legend, myth, or traditional story is situated or associated.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faee7324819090a4c56147cb0bf5 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.