Triple
T9009410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 23 Squadron RAAF |
E215428
|
entity |
| Predicate | supportTo |
P16415
|
FINISHED |
| Object | RAAF flying squadrons based at Amberley |
—
|
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: RAAF flying squadrons based at Amberley | Statement: [No. 23 Squadron RAAF, supportTo, RAAF flying squadrons based at Amberley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportTo Context triple: [No. 23 Squadron RAAF, supportTo, RAAF flying squadrons based at Amberley]
-
A.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
D.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
E.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc69c00ae8819090786385a72e8baf |
completed | April 1, 2026, 12:41 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:06 p.m.