Triple
T4014528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus spacecraft |
E90723
|
entity |
| Predicate | approachPort |
P30512
|
FINISHED |
| Object | Harmony nadir port |
—
|
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: Harmony nadir port | Statement: [Cygnus spacecraft, approachPort, Harmony nadir port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachPort Context triple: [Cygnus spacecraft, approachPort, Harmony nadir port]
-
A.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
-
B.
approachLocation
chosen
Indicates that an entity moves closer to or heads toward a specified location.
-
C.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
D.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.