Triple
T25146185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Officer Commanding No. 18 Group RAF |
E629938
|
entity |
| Predicate | formationCommanded |
P64547
|
FINISHED |
| Object | No. 18 Group RAF |
—
|
NE NERFINISHED |
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: No. 18 Group RAF | Statement: [Air Officer Commanding No. 18 Group RAF, formationCommanded, No. 18 Group RAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationCommanded Context triple: [Air Officer Commanding No. 18 Group RAF, formationCommanded, No. 18 Group RAF]
-
A.
formationTypeCommanded
Indicates that an agent issues an order specifying the type of formation that another entity or group should adopt.
-
B.
commandedFormation
chosen
Indicates that one entity held command authority over a specific military or organizational formation.
-
C.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
D.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
E.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:30 a.m.