Triple
T457969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmark |
E7273
|
entity |
| Predicate | flagAtTimeOfIncident |
P401
|
FINISHED |
| Object | German merchant flag |
—
|
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: German merchant flag | Statement: [Altmark, flagAtTimeOfIncident, German merchant flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagAtTimeOfIncident Context triple: [Altmark, flagAtTimeOfIncident, German merchant flag]
-
A.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
B.
flag
chosen
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
C.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
D.
notableProtectiveIncident
Indicates that a significant event occurred in which one entity protected or defended another in a notable or remarkable way.
-
E.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.