Triple
T26402413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VLBA antenna at Mauna Kea, Hawaii |
E663736
|
entity |
| Predicate | dataSentTo |
P64262
|
FINISHED |
| Object | VLBA correlator |
E1702035
|
NE 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: VLBA correlator | Statement: [VLBA antenna at Mauna Kea, Hawaii, dataSentTo, VLBA correlator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSentTo Context triple: [VLBA antenna at Mauna Kea, Hawaii, dataSentTo, VLBA correlator]
-
A.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
B.
dateSent
Indicates the specific date on which something (such as a message, document, or item) was sent from one party to another.
-
C.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
D.
sentToDestination
chosen
Indicates that something or someone is transferred or dispatched from an origin to a specified destination.
-
E.
sentMembersTo
Indicates that one entity dispatched or assigned its members to another entity or location.
- F. None of above.
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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f55060819081b3e074aefc244e |
completed | May 2, 2026, 2:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a119a8d9c0c81908f9e1cc351167667 |
completed | May 23, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:32 p.m.