Triple
T24082348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA collaboration |
E596536
|
entity |
| Predicate | telescopeTypeUsed |
P2518
|
FINISHED |
| Object | large-sized telescopes |
—
|
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: large-sized telescopes | Statement: [CTA collaboration, telescopeTypeUsed, large-sized telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeTypeUsed Context triple: [CTA collaboration, telescopeTypeUsed, large-sized telescopes]
-
A.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
B.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
C.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
D.
telescopeUnitName
Indicates the specific name assigned to a telescope unit within a larger telescope system or network.
-
E.
notableTelescope
Indicates that the subject is a telescope recognized for its significance, prominence, or special importance in some context.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc257f408190ab87c6f95adca96d |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.