Triple
T23392220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alypius |
E594048
|
entity |
| Predicate | roleInAugustineLife |
P143890
|
FINISHED |
| Object | spiritual companion |
—
|
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: spiritual companion | Statement: [Alypius, roleInAugustineLife, spiritual companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAugustineLife Context triple: [Alypius, roleInAugustineLife, spiritual companion]
-
A.
roleInAristotlesLife
Indicates the specific capacity, function, or relationship an entity had in Aristotle’s life (e.g., teacher, student, patron, family member).
-
B.
roleInSalvationHistory
Indicates the specific function or significance an entity has within the overarching narrative or process of salvation history.
-
C.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
D.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
-
E.
religiousAndSpiritualRole
chosen
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49ca5a0819091b74ca59e7fedd4 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.