Triple
T29375092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Xebel |
E744970
|
entity |
| Predicate | typeOfPowerStructure |
P103958
|
FINISHED |
| Object | royalty |
—
|
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: royalty | Statement: [Queen of Xebel, typeOfPowerStructure, royalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPowerStructure Context triple: [Queen of Xebel, typeOfPowerStructure, royalty]
-
A.
powerStructure
Indicates how authority, control, and decision-making are distributed and organized among entities within a system or group.
-
B.
politicalPowerType
Indicates the specific form or category of political authority or power that an entity holds or exercises.
-
C.
natureOfPower
Indicates the inherent type or character of power that an entity possesses or exercises in a given context.
-
D.
typeOfPolity
chosen
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
E.
seatOfPowerType
Indicates the type or category of a seat of power associated with an entity (e.g., political, religious, administrative).
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 28, 2026, 2:30 p.m.