Triple
T29926689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philip |
E760098
|
entity |
| Predicate | associatedWithMissionaryWorkIn |
P144238
|
FINISHED |
| Object | Asia Minor |
E9845
|
NE 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: Asia Minor | Statement: [Saint Philip, associatedWithMissionaryWorkIn, Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMissionaryWorkIn Context triple: [Saint Philip, associatedWithMissionaryWorkIn, Asia Minor]
-
A.
associatedWithMissionaryHistory
chosen
Indicates a relationship where something is connected or relevant to the activities, legacy, or historical context of missionary work.
-
B.
hasNotableMissionary
Indicates that an entity is associated with, or has, a notable missionary linked to it.
-
C.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
D.
performedMissionaryServiceFor
Indicates that one entity carried out missionary service on behalf of, or under the auspices of, another entity.
-
E.
sentAsMissionaryBy
Indicates that one entity is formally commissioned and dispatched by another entity to serve as a missionary.
- F. None of above.
Provenance (4 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27141fdd5c81909c97d5ee711c88f2 |
completed | June 8, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:16 p.m.