Triple
T25794966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Imperial and Royal Majesty |
E649654
|
entity |
| Predicate | denotesDualRole |
P108317
|
FINISHED |
| Object | Emperor and King |
—
|
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: Emperor and King | Statement: [His Imperial and Royal Majesty, denotesDualRole, Emperor and King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesDualRole Context triple: [His Imperial and Royal Majesty, denotesDualRole, Emperor and King]
-
A.
combinesRoleOf
chosen
Indicates a relationship where a single entity simultaneously fulfills or merges multiple distinct roles or functions.
-
B.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
C.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ff02f0948190b1e3cee38a97105d |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:28 a.m.