Triple
T2144962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Defence Control Centre |
E47042
|
entity |
| Predicate | usesCapability |
P14121
|
FINISHED |
| Object | radar surveillance |
—
|
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 surveillance | Statement: [Air Defence Control Centre, usesCapability, radar surveillance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCapability Context triple: [Air Defence Control Centre, usesCapability, radar surveillance]
-
A.
usedCapability
chosen
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
B.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
C.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
D.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.