Triple
T37883386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardspace: Shipbreaker |
E944929
|
entity |
| Predicate | initialReleaseForm |
P14177
|
FINISHED |
| Object | early access |
—
|
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: early access | Statement: [Hardspace: Shipbreaker, initialReleaseForm, early access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialReleaseForm Context triple: [Hardspace: Shipbreaker, initialReleaseForm, early access]
-
A.
initialPublicationForm
chosen
Indicates the original format or medium in which a work was first published.
-
B.
releaseForm
Indicates that one entity formally authorizes the release or disclosure of information, rights, or responsibilities to another entity through a consent or waiver document.
-
C.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
D.
relaunchForm
Indicates that an existing form is being started again or reactivated, typically after having been closed, submitted, or previously launched.
-
E.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:19 p.m.