Triple
T7481704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatian |
E176772
|
entity |
| Predicate | viewOnIdolatry |
P10116
|
FINISHED |
| Object | strongly opposed pagan idolatry |
—
|
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: strongly opposed pagan idolatry | Statement: [Tatian, viewOnIdolatry, strongly opposed pagan idolatry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnIdolatry Context triple: [Tatian, viewOnIdolatry, strongly opposed pagan idolatry]
-
A.
viewOnWorship
chosen
Indicates a relationship where one entity holds a particular stance, opinion, or doctrinal position regarding the practice or concept of worship.
-
B.
viewOnGod
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
-
C.
viewOnOtherDeities
Indicates how one deity regards, evaluates, or conceptually relates to other deities.
-
D.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
E.
viewOnSeeingGod
Indicates a stance or interpretation someone holds regarding the experience or possibility of seeing God.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f534aa388190b3bb3e16be3a54c8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.