Triple
T11550374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robber Council |
E273873
|
entity |
| Predicate | convenedByTitle |
P12500
|
FINISHED |
| Object | Eastern Roman emperor |
—
|
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: Eastern Roman emperor | Statement: [Robber Council, convenedByTitle, Eastern Roman emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedByTitle Context triple: [Robber Council, convenedByTitle, Eastern Roman emperor]
-
A.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
-
B.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
C.
convenesAs
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
-
D.
canBeConvenedBy
chosen
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
-
E.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.