Triple
T26143371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VLBA antenna at Owens Valley, California |
E659583
|
entity |
| Predicate | dataRecordedAt |
P159579
|
FINISHED |
| Object | VLBA correlator facility |
—
|
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: VLBA correlator facility | Statement: [VLBA antenna at Owens Valley, California, dataRecordedAt, VLBA correlator facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRecordedAt Context triple: [VLBA antenna at Owens Valley, California, dataRecordedAt, VLBA correlator facility]
-
A.
dataRecordedAt
chosen
Indicates that specific data was captured or stored at a particular time or location.
-
B.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
C.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
D.
originallyRecordedAt
Indicates that an audio or video work was first captured or produced at a specific location or venue.
-
E.
laterRecordedAt
Indicates that an event, action, or piece of information was recorded at a time later than another referenced recording 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be63218819089ef0c5eb968db2f |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:21 p.m.