Triple
T34524756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distance Measuring Equipment |
E886369
|
entity |
| Predicate | oftenCoLocatedWith |
P115314
|
FINISHED |
| Object | VOR station |
—
|
NE NERFINISHED |
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: VOR station | Statement: [Distance Measuring Equipment, oftenCoLocatedWith, VOR station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCoLocatedWith Context triple: [Distance Measuring Equipment, oftenCoLocatedWith, VOR station]
-
A.
oftenLocatedAs
Indicates that one entity is frequently found or situated in the same place as another entity.
-
B.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
C.
oftenLocatedNear
chosen
Indicates that one entity is frequently found in close physical proximity to another entity.
-
D.
collectivelyLocatedIn
Indicates that multiple entities are all located within the same place or spatial region considered as a group.
-
E.
collocatedWith
Indicates that two entities are located in the same place or spatial context at the same time.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 2:02 a.m.