Triple
T10993832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pneumatomachianism |
E259812
|
entity |
| Predicate | primaryOpponentsWroteIn |
P96536
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Pneumatomachianism, primaryOpponentsWroteIn, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentsWroteIn Context triple: [Pneumatomachianism, primaryOpponentsWroteIn, Greek]
-
A.
primaryOpponentsArgument
Indicates that the argument specified is the main or central argument presented by an opposing side in a debate or conflict.
-
B.
primaryOpposition
Indicates the main or most significant opposing relationship between two entities, such as their chief rival, counterforce, or contrasting position.
-
C.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
-
D.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
E.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
- F. None of above. chosen
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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d460d88190bff918d6dfdb0f93 |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.