Triple
T4911731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 24 |
E110247
|
entity |
| Predicate | observingNote |
P27296
|
FINISHED |
| Object | appears granular in small 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: appears granular in small telescopes | Statement: [Messier 24, observingNote, appears granular in small telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observingNote Context triple: [Messier 24, observingNote, appears granular in small telescopes]
-
A.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
B.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
C.
isNotedOn
chosen
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
D.
notObservedBy
Indicates that an entity, event, or condition is not detected, recorded, or perceived by a specified observer or observation process.
-
E.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.