Triple
T30246287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French forces |
E769061
|
entity |
| Predicate | developedTactic |
P178239
|
FINISHED |
| Object | combined arms 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: combined arms warfare | Statement: [French forces, developedTactic, combined arms warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedTactic Context triple: [French forces, developedTactic, combined arms warfare]
-
A.
tacticalDevelopment
chosen
Indicates the process by which strategies or methods are refined, adjusted, or evolved to improve effectiveness in achieving specific objectives.
-
B.
tacticOf
Indicates that one entity is a tactic, method, or strategy employed or used by another entity.
-
C.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
-
D.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
E.
tacticInspiredBy
Indicates that a tactic is derived from, influenced by, or modeled after another tactic or source.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 7:39 p.m.