Triple
T4935596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abimelech |
E110803
|
entity |
| Predicate | reignCharacterizedAs |
P10867
|
FINISHED |
| Object | violent |
—
|
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: violent | Statement: [Abimelech, reignCharacterizedAs, violent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignCharacterizedAs Context triple: [Abimelech, reignCharacterizedAs, violent]
-
A.
reignCharacterizedBy
chosen
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
-
B.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
C.
describesReignOf
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
-
D.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706825188190b854dca5ca2f9db6 |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.