Triple
T26309224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaysh al-‘Usrah |
E661771
|
entity |
| Predicate | hasLogisticalCondition |
P28516
|
FINISHED |
| Object | shortage of mounts |
—
|
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: shortage of mounts | Statement: [Jaysh al-‘Usrah, hasLogisticalCondition, shortage of mounts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogisticalCondition Context triple: [Jaysh al-‘Usrah, hasLogisticalCondition, shortage of mounts]
-
A.
hasLogisticalRole
Indicates that an entity holds a responsibility or function related to planning, coordinating, or managing logistical operations or resources.
-
B.
logisticalCharacteristic
chosen
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
C.
logisticalEffect
Indicates the impact that one event, action, or condition has on the planning, coordination, or execution of logistical operations.
-
D.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
E.
availabilityCondition
Indicates the conditions or circumstances under which something is available, applicable, or can be accessed or used.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 26, 2026, 10:21 p.m.