Triple
T8226676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classis Flavia Augusta |
E192189
|
entity |
| Predicate | hasMilitaryCapability |
P2859
|
FINISHED |
| Object | warships |
—
|
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: warships | Statement: [Classis Flavia Augusta, hasMilitaryCapability, warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryCapability Context triple: [Classis Flavia Augusta, hasMilitaryCapability, warships]
-
A.
warfareCapability
chosen
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
B.
hasFireMissionCapability
Indicates that an entity possesses the ability to plan, coordinate, or execute fire missions (such as artillery or indirect fire support) as part of combat operations.
-
C.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
D.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
-
E.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fc10f48190b7e241c89885a478 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.