Triple
T20297110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oerlikon Contraves |
E505377
|
entity |
| Predicate | notableCaliber |
P139580
|
FINISHED |
| Object | 20 mm |
—
|
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: 20 mm | Statement: [Oerlikon Contraves, notableCaliber, 20 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCaliber Context triple: [Oerlikon Contraves, notableCaliber, 20 mm]
-
A.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableArc
Indicates a significant or defining narrative development, transformation, or storyline involving the related entities.
-
E.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
- F. None of above. chosen
Provenance (4 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677095fb481909806214da4002b59 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:16 a.m.