Triple
T21471524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Bomber |
E529743
|
entity |
| Predicate | appliedToPosition |
P4475
|
FINISHED |
| Object | striker |
—
|
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: striker | Statement: [Der Bomber, appliedToPosition, striker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToPosition Context triple: [Der Bomber, appliedToPosition, striker]
-
A.
appliesToPosition
chosen
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
B.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
C.
appliedToStatus
Indicates that an action, rule, or condition is associated with or affects a particular status or state.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea13adfc819093324ae6fe66c3fd |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:18 p.m.