Triple
T31403382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ole Rømer |
E801058
|
entity |
| Predicate | observedCelestialObject |
P74941
|
FINISHED |
| Object | Jupiter |
—
|
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: Jupiter | Statement: [Ole Rømer, observedCelestialObject, Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedCelestialObject Context triple: [Ole Rømer, observedCelestialObject, Jupiter]
-
A.
observedAstronomicalBody
chosen
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
-
B.
observedAstronomicalEvent
Indicates that an entity has witnessed, detected, or recorded a specific astronomical event.
-
C.
isAstronomicalObject
Indicates that something is classified as an astronomical object, such as a star, planet, moon, asteroid, or similar celestial body.
-
D.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
-
E.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:20 p.m.