Triple
T36006614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Lyon I |
E1041287
|
entity |
| Predicate | calledByReason |
P24494
|
FINISHED |
| Object | ongoing conflict with Frederick II |
—
|
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: ongoing conflict with Frederick II | Statement: [Council of Lyon I, calledByReason, ongoing conflict with Frederick II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledByReason Context triple: [Council of Lyon I, calledByReason, ongoing conflict with Frederick II]
-
A.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
-
B.
calledBackBy
Indicates that one entity returns a previous call or contact initiated by another entity.
-
C.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
calledEvent
Indicates that an entity initiated or made a phone call to another entity during a specific event or time.
-
E.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaffab08190abd3717d9fe857ba |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.