Triple
T26211227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VLBA antenna at Hancock, New Hampshire |
E655494
|
entity |
| Predicate | dataCollectedAt |
P160372
|
FINISHED |
| Object | VLBA correlator (via networked data transfer) |
—
|
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 (via networked data transfer) | Statement: [VLBA antenna at Hancock, New Hampshire, dataCollectedAt, VLBA correlator (via networked data transfer)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectedAt Context triple: [VLBA antenna at Hancock, New Hampshire, dataCollectedAt, VLBA correlator (via networked data transfer)]
-
A.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
B.
dataRecordedAt
Indicates that specific data was captured or stored at a particular time or location.
-
C.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
D.
dataProcessedAt
Indicates the time or location at which the data was processed.
-
E.
dataProducedAt
Indicates that specific data is generated, recorded, or created at a particular time or location.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:52 p.m.