Triple
T3548963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Technology Telescope |
E75063
|
entity |
| Predicate | telescopeApertureClass |
P50515
|
FINISHED |
| Object | 3–4 metre class telescope |
—
|
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: 3–4 metre class telescope | Statement: [New Technology Telescope, telescopeApertureClass, 3–4 metre class telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeApertureClass Context triple: [New Technology Telescope, telescopeApertureClass, 3–4 metre class telescope]
-
A.
auxiliaryTelescopeAperture
Indicates that one entity functions as the auxiliary telescope whose aperture (opening/diameter) is being specified or associated with another entity.
-
B.
twinTelescopeAperture
Indicates that two telescopes share the same aperture size or have apertures that are functionally equivalent.
-
C.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
D.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
E.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd278348190ad2fa54f4a423541 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.