Triple
T10037841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise |
E205216
|
entity |
| Predicate | neverEquippedWith |
P1817
|
FINISHED |
| Object | functional main engines for spaceflight |
—
|
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: functional main engines for spaceflight | Statement: [Enterprise, neverEquippedWith, functional main engines for spaceflight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neverEquippedWith Context triple: [Enterprise, neverEquippedWith, functional main engines for spaceflight]
-
A.
notWornBy
Indicates that a particular item or object is explicitly not being worn or used as clothing/accessory by a specified entity.
-
B.
notWornWith
Indicates that one item is not worn at the same time as another item, implying mutual exclusivity in being worn together.
-
C.
cannotBeHeldBy
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
-
D.
doesNotHave
chosen
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
E.
notHeldIn
Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcede428c8190ae115dc3425f9b0e |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.