Triple
T17353307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Befehlstaktik |
E421865
|
entity |
| Predicate | isAnalyzedBy |
P170
|
FINISHED |
| Object | military historians |
—
|
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: military historians | Statement: [Befehlstaktik, isAnalyzedBy, military historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAnalyzedBy Context triple: [Befehlstaktik, isAnalyzedBy, military historians]
-
A.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
analyzes
chosen
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
C.
oftenAnalyzedIn
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
D.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
E.
analysisType
Indicates the specific kind or category of analysis being applied or performed in relation to an entity or dataset.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.