Triple
T31596789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Usworth |
E806237
|
entity |
| Predicate | primaryMissionWWII |
P16542
|
FINISHED |
| Object | air defence |
—
|
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: air defence | Statement: [RAF Usworth, primaryMissionWWII, air defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissionWWII Context triple: [RAF Usworth, primaryMissionWWII, air defence]
-
A.
secondaryMissionWWII
Indicates a secondary or supporting mission carried out during World War II, distinct from the primary operational objective.
-
B.
higherCommandDuringWWII
Indicates that one entity served as the superior military authority or command over another entity during World War II.
-
C.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:31 p.m.