Triple
T36899014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandage–Loeb test |
E911976
|
entity |
| Predicate | proposedInstrument |
P187446
|
FINISHED |
| Object | Extremely Large Telescope |
—
|
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: Extremely Large Telescope | Statement: [Sandage–Loeb test, proposedInstrument, Extremely Large Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedInstrument Context triple: [Sandage–Loeb test, proposedInstrument, Extremely Large Telescope]
-
A.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
B.
introducedInstrument
Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
-
C.
createdInstrument
Indicates that an entity brought into existence or produced a particular instrument or tool.
-
D.
inspiredInstrument
Indicates that one entity served as the creative inspiration or model for the design, creation, or development of another instrument.
-
E.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:13 p.m.