Triple
T19075945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerubbaal |
E466901
|
entity |
| Predicate | armySizeFinal |
P27927
|
FINISHED |
| Object | 300 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: 300 men | Statement: [Jerubbaal, armySizeFinal, 300 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armySizeFinal Context triple: [Jerubbaal, armySizeFinal, 300 men]
-
A.
militarySize
chosen
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
B.
restrictedArmySizeOf
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
-
C.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
D.
soldiersCapacity
Indicates the maximum number of soldiers that an entity can hold, support, or accommodate.
-
E.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.