Triple
T32616311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAN-SPM |
E833793
|
entity |
| Predicate | hasObservatoryCodeType |
P18311
|
FINISHED |
| Object | MPC observatory code |
—
|
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: MPC observatory code | Statement: [OAN-SPM, hasObservatoryCodeType, MPC observatory code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservatoryCodeType Context triple: [OAN-SPM, hasObservatoryCodeType, MPC observatory code]
-
A.
observatoryCode
chosen
Indicates a code that uniquely identifies the observatory associated with an observation or measurement.
-
B.
hasAstronomicalCode
Indicates that an entity is associated with a specific astronomical identification code used in celestial catalogs or classification systems.
-
C.
associatedWithObservatory
Indicates that an entity has a documented relationship, connection, or involvement with a specific observatory.
-
D.
hasObservationFacility
Indicates that an entity possesses or is associated with a facility used for observing, monitoring, or collecting data about something.
-
E.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.