Triple
T141802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swope Telescope |
E2867
|
entity |
| Predicate | usedInProject |
P6780
|
FINISHED |
| Object | supernova surveys at Las Campanas Observatory |
—
|
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: supernova surveys at Las Campanas Observatory | Statement: [Swope Telescope, usedInProject, supernova surveys at Las Campanas Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProject Context triple: [Swope Telescope, usedInProject, supernova surveys at Las Campanas Observatory]
-
A.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
B.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
usedInProductLine
Indicates that something (such as a component, material, or feature) is utilized within a particular product line.
-
D.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.