Triple
T25750260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 433 Eros |
E648452
|
entity |
| Predicate | firstAsteroidOrbitedBySpacecraft |
P193343
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [433 Eros, firstAsteroidOrbitedBySpacecraft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAsteroidOrbitedBySpacecraft Context triple: [433 Eros, firstAsteroidOrbitedBySpacecraft, true]
-
A.
firstOrbitalMission
Indicates that the subject entity carried out or was involved in the earliest orbital spaceflight mission associated with the object entity.
-
B.
firstAsteroidWithSampleReturn
Indicates that the subject is the first asteroid from which a sample was successfully collected and returned to a receiving body (such as Earth).
-
C.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
D.
firstOrbitalMissionOutcome
Indicates the result or status achieved by an entity’s first orbital mission.
-
E.
firstOperationalOrbiter
Indicates that the subject is the first space shuttle orbiter of its kind to become operational within a given program or fleet.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 22, 2026, 4:33 a.m.