Triple
T27929460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altair lunar lander |
E707937
|
entity |
| Predicate | intendedDockingPartner |
P177530
|
FINISHED |
| Object | Orion spacecraft |
—
|
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: Orion spacecraft | Statement: [Altair lunar lander, intendedDockingPartner, Orion spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedDockingPartner Context triple: [Altair lunar lander, intendedDockingPartner, Orion spacecraft]
-
A.
hasDockingPortType
Indicates that one entity possesses or is equipped with a docking port of a specified type or specification.
-
B.
hasDockingType
Indicates the specific docking configuration or method associated with an entity.
-
C.
dockingSystem
Indicates a relationship where one structure or vehicle is equipped with or connected to a system that enables secure docking with another compatible structure or vehicle.
-
D.
intendedPartner
Indicates that one entity is designated or expected to be the future or planned partner (e.g., romantic, marital, or business) of another entity.
-
E.
supportsDockingStations
Indicates that one entity is compatible with and can function correctly when connected to docking stations associated with another entity.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 7:02 p.m.