Triple
T27655209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Node 1 |
E696973
|
entity |
| Predicate | connectedEarlyTo |
P97108
|
FINISHED |
| Object | Zarya Functional Cargo Block |
—
|
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: Zarya Functional Cargo Block | Statement: [ISS Node 1, connectedEarlyTo, Zarya Functional Cargo Block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedEarlyTo Context triple: [ISS Node 1, connectedEarlyTo, Zarya Functional Cargo Block]
-
A.
earlyPresence
chosen
Indicates that one entity is present or arrives earlier than another reference point, event, or entity.
-
B.
connectedToPlace
Indicates that one entity has a spatial, functional, or relational link or association with a specific place.
-
C.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
D.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
E.
arrivalRelatedTo
Indicates that an arrival event is connected or associated with another entity, event, or circumstance.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 2:34 p.m.