Triple
T3736167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatow |
E79590
|
entity |
| Predicate | hasFormerUseNearby |
P51359
|
FINISHED |
| Object | military airfield |
—
|
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: military airfield | Statement: [Gatow, hasFormerUseNearby, military airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerUseNearby Context triple: [Gatow, hasFormerUseNearby, military airfield]
-
A.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
B.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
-
E.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3b399c819091b42209925c0d8f |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.