Triple
T8519517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 42 Wing RAAF elements |
E201660
|
entity |
| Predicate | typeOfCapabilitySupported |
P55904
|
FINISHED |
| Object | airborne early warning |
—
|
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: airborne early warning | Statement: [No. 42 Wing RAAF elements, typeOfCapabilitySupported, airborne early warning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCapabilitySupported Context triple: [No. 42 Wing RAAF elements, typeOfCapabilitySupported, airborne early warning]
-
A.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
-
B.
capabilityType
chosen
Indicates the type or category of capability that an entity possesses or is associated with.
-
C.
isPartOfCapability
Indicates that one capability is a component or sub-function within a broader, composite capability.
-
D.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe627de908190b463da0f26da4ffb |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.