Triple
T6715508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joaquim |
E153256
|
entity |
| Predicate | associatedRoleOfEponym |
P12885
|
FINISHED |
| Object | father of the Virgin Mary |
—
|
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: father of the Virgin Mary | Statement: [Joaquim, associatedRoleOfEponym, father of the Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRoleOfEponym Context triple: [Joaquim, associatedRoleOfEponym, father of the Virgin Mary]
-
A.
hasEponymConnectionTo
Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
-
B.
namedPersonRole
chosen
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
sharesEponymWith
Indicates that two entities are named after the same person, place, or thing (i.e., they share the same eponym).
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1246b748190aed94e8ab8625f7e |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.