Triple
T3396989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owens Valley Radio Observatory |
E71551
|
entity |
| Predicate | hasArrayConfiguration |
P13644
|
FINISHED |
| Object | interferometric array |
—
|
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: interferometric array | Statement: [Owens Valley Radio Observatory, hasArrayConfiguration, interferometric array]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArrayConfiguration Context triple: [Owens Valley Radio Observatory, hasArrayConfiguration, interferometric array]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
C.
hasTableConfiguration
Indicates that an entity is associated with or defined by a specific arrangement or setup of a table and its properties.
-
D.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
E.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c4099081908a236376b4f86900 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.