Triple
T2100861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavius |
E37087
|
entity |
| Predicate | nameStructureRole |
P2555
|
FINISHED |
| Object | can function as part of an emperor's official titulature |
—
|
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: can function as part of an emperor's official titulature | Statement: [Flavius, nameStructureRole, can function as part of an emperor's official titulature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameStructureRole Context triple: [Flavius, nameStructureRole, can function as part of an emperor's official titulature]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
C.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
D.
addressesRole
Indicates that one entity directs communication, content, or action specifically toward another entity in its capacity or function as a particular role.
-
E.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabb512c819087b1d5ec8ef11e63 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.