Triple
T19988424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deir ez-Zor Military Council |
E493994
|
entity |
| Predicate | hasTypeOfForces |
P138231
|
FINISHED |
| Object | light infantry |
—
|
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: light infantry | Statement: [Deir ez-Zor Military Council, hasTypeOfForces, light infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfForces Context triple: [Deir ez-Zor Military Council, hasTypeOfForces, light infantry]
-
A.
typeOfForcesDirected
Indicates that certain forces are oriented or directed toward a particular target, direction, or reference.
-
B.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
C.
hasComponentForces
Indicates that a composite force is associated with, or can be decomposed into, specific component forces.
-
D.
hasSecondaryForces
Indicates that an entity is subject to or associated with additional, indirect, or supporting forces beyond its primary forces.
-
E.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
- F. None of above. chosen
Provenance (4 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fddfee081909aa8cd6e279b2a7a |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:30 p.m.