Triple
T23758280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Longewala |
E587178
|
entity |
| Predicate | defendingForceSize |
P87717
|
FINISHED |
| Object | about 120 Indian soldiers |
—
|
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: about 120 Indian soldiers | Statement: [Battle of Longewala, defendingForceSize, about 120 Indian soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendingForceSize Context triple: [Battle of Longewala, defendingForceSize, about 120 Indian soldiers]
-
A.
hasApproximateDefendingForceSize
chosen
Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
-
B.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
C.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
D.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
-
E.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdaf52848190b034208de4c4e01a |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.