Triple
T5445235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Northolt |
E122231
|
entity |
| Predicate | roleInSecondWorldWar |
P16542
|
FINISHED |
| Object | fighter station in the defence of London |
—
|
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: fighter station in the defence of London | Statement: [RAF Northolt, roleInSecondWorldWar, fighter station in the defence of London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSecondWorldWar Context triple: [RAF Northolt, roleInSecondWorldWar, fighter station in the defence of London]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
C.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
D.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
E.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.