Triple
T4805957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dragoon |
E106947
|
entity |
| Predicate | hasTacticalRole |
P9463
|
FINISHED |
| Object | mounted 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: mounted infantry | Statement: [dragoon, hasTacticalRole, mounted infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTacticalRole Context triple: [dragoon, hasTacticalRole, mounted infantry]
-
A.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
B.
hasTacticalMobility
Indicates the capability of an entity to move or be repositioned quickly and effectively within a tactical or operational context.
-
C.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
hasStrategicFunction
Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
-
E.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.