Triple
T24981754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nethanel son of Zuar |
E625186
|
entity |
| Predicate | appointedAsLeaderUnder |
P8553
|
FINISHED |
| Object | command of the LORD |
—
|
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: command of the LORD | Statement: [Nethanel son of Zuar, appointedAsLeaderUnder, command of the LORD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsLeaderUnder Context triple: [Nethanel son of Zuar, appointedAsLeaderUnder, command of the LORD]
-
A.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
B.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
C.
promotedLeader
Indicates that one entity has elevated another entity to a higher leadership position or role.
-
D.
namedByLeader
Indicates that an entity has been given its name by a specific leader or person in authority.
-
E.
appointedAs
chosen
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.