Triple
T38233725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eranistes |
E1013561
|
entity |
| Predicate | theologicalPositionOfAuthor |
P100549
|
FINISHED |
| Object | Antiochene tradition |
—
|
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: Antiochene tradition | Statement: [Eranistes, theologicalPositionOfAuthor, Antiochene tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theologicalPositionOfAuthor Context triple: [Eranistes, theologicalPositionOfAuthor, Antiochene tradition]
-
A.
associatedTheologian
Indicates a relationship where a theologian is connected or linked to a particular subject, work, institution, or context.
-
B.
positionOnTheology
Indicates a stance, viewpoint, or opinion that one entity holds regarding theological beliefs, doctrines, or issues.
-
C.
hasAuthorTheologicalAffiliation
chosen
Indicates that an author is associated with a particular theological tradition, denomination, or belief system.
-
D.
writtenByClergyOrTheologian
Indicates that the work or text was authored by a member of the clergy or a professional theologian.
-
E.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.