Triple
T26629332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZIMPOL |
E668448
|
entity |
| Predicate | hostTelescopeUnit |
P76520
|
FINISHED |
| Object | VLT Unit Telescope 3 |
—
|
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: VLT Unit Telescope 3 | Statement: [ZIMPOL, hostTelescopeUnit, VLT Unit Telescope 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTelescopeUnit Context triple: [ZIMPOL, hostTelescopeUnit, VLT Unit Telescope 3]
-
A.
hostTelescopeAgency
Indicates that an agency is responsible for operating, managing, or hosting a particular telescope.
-
B.
telescopeUnitName
chosen
Indicates the specific name assigned to a telescope unit within a larger telescope system or network.
-
C.
locationOnTelescope
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
D.
telescopeMountedOn
Indicates that a telescope is physically installed or fixed onto a specific supporting structure or platform.
-
E.
hostsTelescope
Indicates that one entity provides a location or facility where a telescope is installed, maintained, or operated.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615ec89f081909007ddbe9d99f074 |
completed | May 2, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:24 a.m.