Triple
T6237871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relics of Saint Jerome |
E139520
|
entity |
| Predicate | linkedToPersonRole |
P4342
|
FINISHED |
| Object | Christian priest |
—
|
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: Christian priest | Statement: [Relics of Saint Jerome, linkedToPersonRole, Christian priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToPersonRole Context triple: [Relics of Saint Jerome, linkedToPersonRole, Christian priest]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
C.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
D.
connectsRole
Indicates a relationship in which one entity is linked to another by assigning or associating a specific role between them.
-
E.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0630373088190a9d4b1f7e442c129 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.