Triple
T6521680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | División de Caballería Blindada |
E151197
|
entity |
| Predicate | conflictTypePreparedFor |
P14699
|
FINISHED |
| Object | conventional 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: conventional warfare | Statement: [División de Caballería Blindada, conflictTypePreparedFor, conventional warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypePreparedFor Context triple: [División de Caballería Blindada, conflictTypePreparedFor, conventional warfare]
-
A.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
builtForConflict
chosen
Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
-
C.
conflictPreserved
Indicates that an existing conflict or incompatibility between entities is maintained and not resolved or removed.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
conflictCondition
Indicates that a situation exists in which two or more conditions, actions, or states are incompatible, opposed, or cannot be satisfied simultaneously.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad9431f081909b14b3df3414a55f |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.