Triple
T26718705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deflectors |
E673638
|
entity |
| Predicate | featuresSpaceSetting |
P32516
|
FINISHED |
| Object | starship The Orville |
—
|
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: starship The Orville | Statement: [Deflectors, featuresSpaceSetting, starship The Orville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSpaceSetting Context triple: [Deflectors, featuresSpaceSetting, starship The Orville]
-
A.
featuresSetting
chosen
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
B.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
C.
featuresService
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
D.
featureSet
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 3:39 a.m.