Triple
T35739761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorer 49 |
E1033000
|
entity |
| Predicate | discovererOrMaker |
P412
|
FINISHED |
| Object | NASA Goddard Space Flight Center |
—
|
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: NASA Goddard Space Flight Center | Statement: [Explorer 49, discovererOrMaker, NASA Goddard Space Flight Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discovererOrMaker Context triple: [Explorer 49, discovererOrMaker, NASA Goddard Space Flight Center]
-
A.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
B.
discovererDesignation
Indicates the identifier or designation assigned to the entity that discovered another entity.
-
C.
discovererOrFirstCataloger
Indicates that one entity is the person or agent who first discovered or formally cataloged another entity.
-
D.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
E.
discovererRole
Indicates the role or capacity in which an entity participates as the discoverer of something.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:06 p.m.