Triple
T17541820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACAN |
E427216
|
entity |
| Predicate | canBeCollocatedWith |
P43091
|
FINISHED |
| Object | VOR |
—
|
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: VOR | Statement: [TACAN, canBeCollocatedWith, VOR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCollocatedWith Context triple: [TACAN, canBeCollocatedWith, VOR]
-
A.
collocatedWith
chosen
Indicates that two entities are located in the same place or spatial context at the same time.
-
B.
hasCollocationInformation
Indicates that there is information about how a term or expression typically co-occurs with other words or phrases in usage.
-
C.
canCoexistWith
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
D.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
E.
isInSameRegionAs
Indicates that two entities are located within the same defined geographic or administrative region.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4545e64448190a2a63bc13f549027 |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.