Triple
T5797065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghlabid dynasty |
E128532
|
entity |
| Predicate | militaryFocus |
P17742
|
FINISHED |
| Object | Mediterranean naval warfare |
—
|
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: Mediterranean naval warfare | Statement: [Aghlabid dynasty, militaryFocus, Mediterranean naval warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryFocus Context triple: [Aghlabid dynasty, militaryFocus, Mediterranean naval warfare]
-
A.
militaryDomain
chosen
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
B.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
C.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
D.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
E.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.