Triple
T28773592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | revolt of Basiliscus |
E726474
|
entity |
| Predicate | hasResultingTitleForLeader |
P200202
|
FINISHED |
| Object | Eastern Roman Emperor |
—
|
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: Eastern Roman Emperor | Statement: [revolt of Basiliscus, hasResultingTitleForLeader, Eastern Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResultingTitleForLeader Context triple: [revolt of Basiliscus, hasResultingTitleForLeader, Eastern Roman Emperor]
-
A.
hasCollectiveLeaderTitle
Indicates that a collective entity (such as a group, organization, or body) holds or is associated with a specific leadership title.
-
B.
hasStateLeaderTitle
Indicates the official title held by the leader of a state.
-
C.
supportedLeaderTitle
Indicates that an entity held a position or title in support of, or subordinate to, a specified leader.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: April 28, 2026, 6:16 a.m.