Triple
T26176970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z84C00 |
E654567
|
entity |
| Predicate | IOSpace |
P160021
|
FINISHED |
| Object | 256 I/O ports |
—
|
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: 256 I/O ports | Statement: [Z84C00, IOSpace, 256 I/O ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IOSpace Context triple: [Z84C00, IOSpace, 256 I/O ports]
-
A.
mainSpaceStation
Indicates that one entity serves as the primary or central space station associated with another entity.
-
B.
spaceStationType
Indicates the specific functional or structural category to which a space station belongs (e.g., research, military, commercial).
-
C.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
D.
spaceStationServed
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
-
E.
isPrimarySpaceportOf
Indicates that a given spaceport serves as the main or principal launch and operations facility for a specified region, organization, or celestial body.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:38 p.m.