Triple
T25994052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalthea |
E646436
|
entity |
| Predicate | observedInDetailBy |
P1165
|
FINISHED |
| Object | Galileo orbiter |
—
|
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: Galileo orbiter | Statement: [Amalthea, observedInDetailBy, Galileo orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInDetailBy Context triple: [Amalthea, observedInDetailBy, Galileo orbiter]
-
A.
observedBy
chosen
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
B.
observedVia
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
C.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
D.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
E.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 8:57 a.m.