Triple
T3878832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 29 Squadron RAF |
E92570
|
entity |
| Predicate | forceElement |
P52099
|
FINISHED |
| Object | Quick Reaction Alert support |
—
|
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: Quick Reaction Alert support | Statement: [No. 29 Squadron RAF, forceElement, Quick Reaction Alert support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceElement Context triple: [No. 29 Squadron RAF, forceElement, Quick Reaction Alert support]
-
A.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
C.
forceSize
Indicates a relationship where one entity specifies or constrains the magnitude or size of a force associated with another entity.
-
D.
forceStructure
Indicates a relationship where one entity imposes or defines the structural arrangement, organization, or configuration of another entity.
-
E.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
- F. None of above. chosen
Provenance (4 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.