Triple
T35561212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009-071A |
E1027638
|
entity |
| Predicate | NEOWISEMissionType |
P183249
|
FINISHED |
| Object | near-Earth object survey |
—
|
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: near-Earth object survey | Statement: [2009-071A, NEOWISEMissionType, near-Earth object survey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NEOWISEMissionType Context triple: [2009-071A, NEOWISEMissionType, near-Earth object survey]
-
A.
planetaryMissionType
Indicates the specific category or nature of a mission conducted to explore or study a planet or planetary body.
-
B.
spacecraftOfMission
Indicates that a given spacecraft is the one used or assigned for a particular mission.
-
C.
spacecraftPlanned
Indicates that a spacecraft is scheduled or intended to be launched, operated, or utilized in the future according to a plan or mission design.
-
D.
spaceTelescope
Indicates a relationship where an entity functions as or is classified as a space-based telescope used for astronomical observation beyond Earth's atmosphere.
-
E.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.