Triple
T20950148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palomar 48-inch Schmidt Telescope |
E515954
|
entity |
| Predicate | laterDetector |
P141827
|
FINISHED |
| Object | charge-coupled devices |
—
|
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: charge-coupled devices | Statement: [Palomar 48-inch Schmidt Telescope, laterDetector, charge-coupled devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDetector Context triple: [Palomar 48-inch Schmidt Telescope, laterDetector, charge-coupled devices]
-
A.
laterFlag
Indicates that one event, state, or action occurs at a time later than another referenced event, state, or action.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
laterSought
Indicates that one entity attempted to obtain, pursue, or request another entity at a subsequent time relative to some prior reference point.
-
D.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery of another entity.
-
E.
laterController
Indicates that one entity assumes control, authority, or responsibility after another entity, succeeding it in time.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadd3bd88190a0d1fdea9d300fc0 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 1:23 p.m.