Triple
T1013501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing X-37 |
E21876
|
entity |
| Predicate | firstOrbitalMission |
P23257
|
FINISHED |
| Object | April 2010 |
—
|
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: April 2010 | Statement: [Boeing X-37, firstOrbitalMission, April 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOrbitalMission Context triple: [Boeing X-37, firstOrbitalMission, April 2010]
-
A.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
-
B.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
C.
firstHumanToOrbitEarth
Indicates that the subject is the first human who successfully completed an orbital flight around Earth.
-
D.
firstSuccessfulOrbitalLaunchVehicle
Indicates that the subject is the launch vehicle that achieved the first successful orbital launch for the associated space program, organization, or country.
-
E.
firstHumanInSpace
Indicates that the subject is the first human ever to travel into outer space.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.