Triple
T25859528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPT-3G survey |
E651443
|
entity |
| Predicate | telescopeGeneration |
P159357
|
FINISHED |
| Object | third-generation camera |
—
|
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: third-generation camera | Statement: [SPT-3G survey, telescopeGeneration, third-generation camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeGeneration Context triple: [SPT-3G survey, telescopeGeneration, third-generation camera]
-
A.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
B.
notableTelescope
Indicates that the subject is a telescope recognized for its significance, prominence, or special importance in some context.
-
C.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
D.
numberOfTelescopes
Indicates the quantity of telescopes associated with a given entity or context.
-
E.
telescopeDesign
Indicates a relationship where one entity is responsible for creating, specifying, or determining the structural and functional design of a telescope used by another entity or for a particular purpose.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026a80208190a8b1fae20d6ed906 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 8:05 a.m.