Triple
T1467165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallicanism |
E27050
|
entity |
| Predicate | positionOnCouncils |
P28872
|
FINISHED |
| Object | affirmed superiority of general councils over the pope |
—
|
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: affirmed superiority of general councils over the pope | Statement: [Gallicanism, positionOnCouncils, affirmed superiority of general councils over the pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCouncils Context triple: [Gallicanism, positionOnCouncils, affirmed superiority of general councils over the pope]
-
A.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
B.
hasCouncilSeat
Indicates that an entity holds a position or seat on a governing council.
-
C.
definedAtCouncil
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
-
D.
seatOfCouncil
Indicates that a location serves as the official meeting place or headquarters of a council.
-
E.
councilLocation
Indicates that a governing council is located or based at a particular place or venue.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5bcfa0881909d6137c69825bc7a |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:01 p.m.