Triple
T4852460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uriah the Hittite |
E108447
|
entity |
| Predicate | commandChain |
P3671
|
FINISHED |
| Object | under Joab |
—
|
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: under Joab | Statement: [Uriah the Hittite, commandChain, under Joab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandChain Context triple: [Uriah the Hittite, commandChain, under Joab]
-
A.
commandsThrough
chosen
Indicates that one entity exercises authority or control over another indirectly, acting through an intermediary or chain of command.
-
B.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
C.
missionChainOrder
Indicates the sequential ordering relationship between missions within a mission chain, specifying which mission must occur before another.
-
D.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
E.
commandProcessor
Indicates that one entity is responsible for receiving, interpreting, and executing commands issued by 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.