Triple
T29375101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Xebel |
E744970
|
entity |
| Predicate | hasPowerContext |
P194009
|
FINISHED |
| Object | underwater politics |
—
|
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: underwater politics | Statement: [Queen of Xebel, hasPowerContext, underwater politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerContext Context triple: [Queen of Xebel, hasPowerContext, underwater politics]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
hasPowerBase
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
C.
hasPowerFunction
Indicates that one entity serves as the power function or exponentiation operation applied to another entity.
-
D.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
-
E.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
- F. None of above. chosen
Provenance (4 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 28, 2026, 2:30 p.m.