Triple
T27467547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (test orbiter) |
E693215
|
entity |
| Predicate | lacksComponent |
P1817
|
FINISHED |
| Object | space-rated systems |
—
|
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: space-rated systems | Statement: [Enterprise (test orbiter), lacksComponent, space-rated systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lacksComponent Context triple: [Enterprise (test orbiter), lacksComponent, space-rated systems]
-
A.
doesNotHave
chosen
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
B.
doesNotUseComponent
Indicates that one entity explicitly avoids or omits using a particular component in its structure, behavior, or implementation.
-
C.
skeletonLacks
Indicates that an entity’s skeleton does not possess or is missing a specified bone, feature, or structural component.
-
D.
doesNotProvideFor
Indicates that one entity fails or is not responsible for supplying support, resources, or necessary provisions to another entity.
-
E.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 12:52 p.m.