Triple
T36547087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ar-Pharazôn |
E901165
|
entity |
| Predicate | seizesPowerBy |
P185837
|
FINISHED |
| Object | Forced marriage to Míriel |
—
|
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: Forced marriage to Míriel | Statement: [Ar-Pharazôn, seizesPowerBy, Forced marriage to Míriel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seizesPowerBy Context triple: [Ar-Pharazôn, seizesPowerBy, Forced marriage to Míriel]
-
A.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
usurpsThroneFrom
Indicates that one entity seizes control of a throne or rulership position that previously belonged to another entity, typically by force or illegitimate means.
-
C.
assignsExecutivePowerTo
Indicates that executive authority or decision-making power is formally granted from one entity to another.
-
D.
seizedPowerAfter
Indicates that one entity took control or authority from another entity following a specified event or point in time.
-
E.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.