Triple
T13439671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Exalted Highness |
E320324
|
entity |
| Predicate | hasSemanticType |
P7975
|
FINISHED |
| Object | style of sovereignty |
—
|
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: style of sovereignty | Statement: [His Exalted Highness, hasSemanticType, style of sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSemanticType Context triple: [His Exalted Highness, hasSemanticType, style of sovereignty]
-
A.
hasSemantics
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
B.
semanticType
chosen
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
-
C.
hasSemanticsDefinedBy
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
D.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
E.
hasLinguisticDataType
Indicates that something is associated with or characterized by a specific type or category of linguistic data.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee5ec488190bd0c1e990dbd2bc2 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.