Triple
T12618616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Constantinople 867 |
E301319
|
entity |
| Predicate | tookStanceOn |
P21606
|
FINISHED |
| Object | jurisdiction over Bulgaria |
—
|
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: jurisdiction over Bulgaria | Statement: [Council of Constantinople 867, tookStanceOn, jurisdiction over Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookStanceOn Context triple: [Council of Constantinople 867, tookStanceOn, jurisdiction over Bulgaria]
-
A.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
B.
editorialStance
Indicates the position, viewpoint, or bias an editor or publication adopts toward a subject, issue, or entity.
-
C.
conflictStance
Indicates a party’s position, attitude, or alignment regarding a particular conflict or dispute.
-
D.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
E.
tookPositionOn
chosen
Indicates that an entity expressed or adopted a specific stance, opinion, or viewpoint regarding a particular issue, topic, or subject.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.