Triple
T3834150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSS Unity |
E91086
|
entity |
| Predicate | commercialServiceStart |
P35191
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [VSS Unity, commercialServiceStart, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialServiceStart Context triple: [VSS Unity, commercialServiceStart, 2023]
-
A.
announcedCommercialService
Indicates that an entity has publicly declared the start or availability of a commercial service involving another entity.
-
B.
commercialIntroduction
Indicates that one entity introduces or connects another entity to a commercial opportunity, partner, product, or service for business purposes.
-
C.
openedForCommercialService
chosen
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
D.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
commercialStatus
Indicates the current state or condition of something in terms of its commercial availability, activity, or market use.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.