Triple
T21288485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4548 |
E524722
|
entity |
| Predicate | isObservableWith |
P132924
|
FINISHED |
| Object | amateur 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: amateur telescopes | Statement: [NGC 4548, isObservableWith, amateur telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservableWith Context triple: [NGC 4548, isObservableWith, amateur telescopes]
-
A.
hasObservable
Indicates that an entity is associated with, or gives rise to, a measurable or perceivable outcome, property, or effect.
-
B.
isObservedUsing
chosen
Indicates that an entity is observed or monitored by means of a specified instrument, method, or medium.
-
C.
isKeyObservableFor
Indicates that a particular key or identifier can be observed, detected, or monitored within a given context or system.
-
D.
isObservedFrom
Indicates that one entity serves as the vantage point or location from which another entity is perceived, measured, or monitored.
-
E.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d7c57c8190bc4180ea590a62d4 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.