Triple
T31704374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUROPAAMS |
E809139
|
entity |
| Predicate | systemTypeDeveloped |
P15304
|
FINISHED |
| Object | shipborne air-defence system |
—
|
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: shipborne air-defence system | Statement: [EUROPAAMS, systemTypeDeveloped, shipborne air-defence system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemTypeDeveloped Context triple: [EUROPAAMS, systemTypeDeveloped, shipborne air-defence system]
-
A.
systemType
chosen
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
-
C.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
D.
developedOn
Indicates that something was created, built, or produced using a particular platform, technology, or environment.
-
E.
platformDeveloped
Indicates that a particular platform has been created, built, or produced by a specified developer or organization.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:13 p.m.