Triple
T24547117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European VLBI Network |
E607255
|
entity |
| Predicate | dataProcessedAt |
P156272
|
FINISHED |
| Object | JIVE correlator |
—
|
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: JIVE correlator | Statement: [European VLBI Network, dataProcessedAt, JIVE correlator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProcessedAt Context triple: [European VLBI Network, dataProcessedAt, JIVE correlator]
-
A.
dataProducedAt
Indicates that specific data is generated, recorded, or created at a particular time or location.
-
B.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
C.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
D.
treatedAt
Indicates that a person or patient received medical care or treatment at a particular healthcare facility or location.
-
E.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.