Triple
T2373367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Observatories program |
E46138
|
entity |
| Predicate | observationPlatform |
P38767
|
FINISHED |
| Object | Earth orbit |
—
|
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: Earth orbit | Statement: [Great Observatories program, observationPlatform, Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationPlatform Context triple: [Great Observatories program, observationPlatform, Earth orbit]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
C.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
D.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
E.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
- F. None of above. chosen
Provenance (4 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:56 p.m.