Triple
T35731255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubi periculum |
E1032756
|
entity |
| Predicate | promulgatedAtCouncil |
P7823
|
FINISHED |
| Object | Second Council of Lyon |
—
|
NE NERFINISHED |
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: Second Council of Lyon | Statement: [Ubi periculum, promulgatedAtCouncil, Second Council of Lyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promulgatedAtCouncil Context triple: [Ubi periculum, promulgatedAtCouncil, Second Council of Lyon]
-
A.
promulgatedAt
Indicates the time or date at which an official rule, law, or document is formally issued or put into effect.
-
B.
definedAtCouncil
chosen
Indicates that something was formally established, decided, or codified during a council or official deliberative meeting.
-
C.
promulgatedFor
Indicates that something, such as a law, rule, or decree, has been formally issued or enacted for a particular entity, group, or context.
-
D.
councilConvokedBy
Indicates that a council or formal assembly was called together or convened by a particular person, group, or authority.
-
E.
councilPresidedOverBy
Indicates that a council or formal assembly is led, directed, or overseen by a particular person or authority.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.