Triple
T4879491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deborah |
E109288
|
entity |
| Predicate | commandedBarakToMuster |
P17766
|
FINISHED |
| Object | ten thousand men |
—
|
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: ten thousand men | Statement: [Deborah, commandedBarakToMuster, ten thousand men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedBarakToMuster Context triple: [Deborah, commandedBarakToMuster, ten thousand men]
-
A.
commandedTo
chosen
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
B.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
C.
commandedFor
Indicates that one entity issued an order or directive on behalf of, or in service of, another entity or purpose.
-
D.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
E.
garrisonCommand
Indicates that one entity holds command authority over the garrison or stationed military forces at a particular location.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.