Triple
T795805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyson sphere concept |
E17016
|
entity |
| Predicate | DysonShellDefinition |
P7380
|
FINISHED |
| Object | rigid continuous shell completely enclosing a star |
—
|
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: rigid continuous shell completely enclosing a star | Statement: [Dyson sphere concept, DysonShellDefinition, rigid continuous shell completely enclosing a star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DysonShellDefinition Context triple: [Dyson sphere concept, DysonShellDefinition, rigid continuous shell completely enclosing a star]
-
A.
shellType
chosen
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
-
B.
definesDeviceType
Indicates that one entity specifies or assigns the device type classification of another entity.
-
C.
componentsDefinition
Indicates that one entity defines or specifies the components that make up another entity.
-
D.
hasShell
Indicates that an entity possesses or is covered by a shell as a physical protective structure.
-
E.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b04cd8819092e2fd7ba4df8672 |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.