Triple
T29173513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Faustinus |
E739538
|
entity |
| Predicate | hasLegendaryActs |
P170938
|
FINISHED |
| Object | Acts of Saints Faustinus and Jovita |
—
|
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: Acts of Saints Faustinus and Jovita | Statement: [Saint Faustinus, hasLegendaryActs, Acts of Saints Faustinus and Jovita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryActs Context triple: [Saint Faustinus, hasLegendaryActs, Acts of Saints Faustinus and Jovita]
-
A.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
-
B.
hasActs
Indicates that an entity is associated with one or more actions, performances, or deeds it carries out or is responsible for.
-
C.
hasIconicPerformanceBy
Indicates that something (such as a work, event, or production) features a particularly memorable or defining performance by a specific performer.
-
D.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
E.
hasCultOrLegend
chosen
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 11:53 a.m.