Triple
T28971796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muslim emirates of the Near East |
E734293
|
entity |
| Predicate | hasMilitaryForces |
P104865
|
FINISHED |
| Object | cavalry |
—
|
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: cavalry | Statement: [Muslim emirates of the Near East, hasMilitaryForces, cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryForces Context triple: [Muslim emirates of the Near East, hasMilitaryForces, cavalry]
-
A.
hasArmedForces
chosen
Indicates that an entity possesses or maintains organized military forces under its control.
-
B.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
-
C.
hasMilitaryPresence
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
D.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 9:06 a.m.