Triple
T4760990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gideon |
E105695
|
entity |
| Predicate | militaryForceSize |
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: [Gideon, militaryForceSize, 300 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryForceSize Context triple: [Gideon, militaryForceSize, 300 men]
-
A.
militarySize
chosen
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
B.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
E.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.