Triple
T35482216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Six Kingdoms |
E1025497
|
entity |
| Predicate | holdsPowerOver |
P6502
|
FINISHED |
| Object | Crownlands |
—
|
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: Crownlands | Statement: [King of the Six Kingdoms, holdsPowerOver, Crownlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsPowerOver Context triple: [King of the Six Kingdoms, holdsPowerOver, Crownlands]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
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.
-
D.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
-
E.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.