Triple
T3746809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroradar consortium |
E81228
|
entity |
| Predicate | hasComponentResponsibility |
P51082
|
FINISHED |
| Object | radar hardware design |
—
|
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: radar hardware design | Statement: [Euroradar consortium, hasComponentResponsibility, radar hardware design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentResponsibility Context triple: [Euroradar consortium, hasComponentResponsibility, radar hardware design]
-
A.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
B.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
C.
hasComponentCurrent
Indicates that an entity currently includes or contains a specific component as part of its present composition or structure.
-
D.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
E.
hasServerComponent
Indicates that an entity includes, depends on, or is associated with a particular server-side component.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb69887c8190a3f1188ec85727b0 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc1560c248190b07438d766880990 |
completed | March 8, 2026, 6:35 p.m. |
Created at: March 8, 2026, 3:35 p.m.