Triple
T14745871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seydlitz-class battlecruiser |
E346465
|
entity |
| Predicate | designedForConflict |
P14699
|
FINISHED |
| Object | potential North Sea engagements |
—
|
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: potential North Sea engagements | Statement: [Seydlitz-class battlecruiser, designedForConflict, potential North Sea engagements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForConflict Context triple: [Seydlitz-class battlecruiser, designedForConflict, potential North Sea engagements]
-
A.
builtForConflict
chosen
Indicates that something is specifically designed or intended to function effectively in situations of conflict or confrontation.
-
B.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
C.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
D.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d002708190a32a4a45e96fc389 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.