Triple
T37036650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble L |
E916657
|
entity |
| Predicate | hasImagingSource |
P141015
|
FINISHED |
| Object | Lunar Orbiter missions |
—
|
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: Lunar Orbiter missions | Statement: [Hubble L, hasImagingSource, Lunar Orbiter missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImagingSource Context triple: [Hubble L, hasImagingSource, Lunar Orbiter missions]
-
A.
hasImagingType
Indicates the specific imaging modality or technique associated with or used in a given imaging procedure or result.
-
B.
hasImagingCadence
Indicates the regular interval or frequency at which imaging observations are repeatedly acquired.
-
C.
hasDiscoveryImageSource
chosen
Indicates the source or origin (such as a survey, instrument, or dataset) from which the discovery image of an entity was obtained.
-
D.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
E.
hasCamera
Indicates that an entity is equipped with or possesses a camera.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:14 p.m.