Triple
T8465588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAAF PC-21 aircraft (for JTAC support via No. 4 Squadron) |
E200152
|
entity |
| Predicate | configuredFor |
P13644
|
FINISHED |
| Object | JTAC training missions |
—
|
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: JTAC training missions | Statement: [RAAF PC-21 aircraft (for JTAC support via No. 4 Squadron), configuredFor, JTAC training missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configuredFor Context triple: [RAAF PC-21 aircraft (for JTAC support via No. 4 Squadron), configuredFor, JTAC training missions]
-
A.
appliesToConfiguration
Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
-
B.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
C.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
D.
partlyConfiguredAs
Indicates that one entity is only partially set up, arranged, or defined to function as another entity or in another role.
-
E.
configurationAvailable
Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d17ec8819093becdaec750aff5 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.