Triple
T3462379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libius Severus |
E73054
|
entity |
| Predicate | legitimacyIssues |
P30299
|
FINISHED |
| Object | lack of recognition by Constantinople |
—
|
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: lack of recognition by Constantinople | Statement: [Libius Severus, legitimacyIssues, lack of recognition by Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legitimacyIssues Context triple: [Libius Severus, legitimacyIssues, lack of recognition by Constantinople]
-
A.
legitimacyPerception
Indicates how legitimate or appropriate an entity, action, or authority is perceived to be by relevant observers or stakeholders.
-
B.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
C.
illegitimacyDeclaredBy
chosen
Indicates that an authority or entity has formally declared a person, status, or act to be illegitimate.
-
D.
legalStatusDebatedBy
Indicates that the legal status of an entity is the subject of dispute, discussion, or controversy among parties or authorities.
-
E.
treatyOrLegalIssue
Indicates a formal agreement, dispute, or matter governed by treaties or legal frameworks between parties.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.