Triple
T29340986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Executor |
E744035
|
entity |
| Predicate | featuresEnvironmentType |
P13810
|
FINISHED |
| Object | Imperial starship |
—
|
NE NERFINISHED |
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: Imperial starship | Statement: [The Executor, featuresEnvironmentType, Imperial starship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnvironmentType Context triple: [The Executor, featuresEnvironmentType, Imperial starship]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
C.
environmentClass
Indicates that an entity belongs to, or is categorized within, a particular type or class of environment.
-
D.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
E.
environmentSubtype
Indicates that one environment is a more specific subtype or category within another, more general environment.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 28, 2026, 1:33 p.m.