Triple
T37339980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christotokos |
E927005
|
entity |
| Predicate | wasOpposedInYear |
P187987
|
FINISHED |
| Object | 431 |
—
|
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: 431 | Statement: [Christotokos, wasOpposedInYear, 431]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOpposedInYear Context triple: [Christotokos, wasOpposedInYear, 431]
-
A.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
B.
hasOpposedParty
Indicates that one party is in an opposing or adversarial position relative to another party, typically within a dispute, conflict, or legal proceeding.
-
C.
hasOppositionRoleSince
Indicates that an entity has held a specific opposition role or position continuously since a given point in time.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
wasOppositionStrongholdDuring
Indicates that a particular place served as a primary base or strong area of support for an opposition group during a specified time period.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.