Triple
T4264418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen Telescope Array |
E96788
|
entity |
| Predicate | correlatorType |
P55052
|
FINISHED |
| Object | wide-field imaging correlator |
—
|
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: wide-field imaging correlator | Statement: [Allen Telescope Array, correlatorType, wide-field imaging correlator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correlatorType Context triple: [Allen Telescope Array, correlatorType, wide-field imaging correlator]
-
A.
hasCorrelativesSystem
Indicates that one entity possesses or employs a system of correlatives—structured, corresponding elements or forms that are systematically related to each other.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
D.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fc94f64819091f438d8ae5ed687 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.