Triple
T539389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatow Airfield |
E12395
|
entity |
| Predicate | capturedIn |
P16653
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Gatow Airfield, capturedIn, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedIn Context triple: [Gatow Airfield, capturedIn, 1945]
-
A.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
B.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
-
C.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
D.
capturedPlace
Indicates that an agent took control of or seized a specific place, typically through force or strategic action.
-
E.
capturedEquipment
Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.