Triple
T21649370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jehu |
E534295
|
entity |
| Predicate | militaryRankBeforeKingship |
P80252
|
FINISHED |
| Object | army commander |
—
|
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: army commander | Statement: [Jehu, militaryRankBeforeKingship, army commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankBeforeKingship Context triple: [Jehu, militaryRankBeforeKingship, army commander]
-
A.
militaryRankBeforeAccession
chosen
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
-
B.
militaryRankBeforeSultan
Indicates that one entity held a specific military rank prior to becoming a sultan.
-
C.
rankBeforeKingship
Indicates that one entity held a higher or earlier rank or status than another entity prior to that other entity attaining kingship.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
militaryRankScope
Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational context.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59131c88819082df8e5b87f5954b |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.