Triple
T22412890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Persei 1901 |
E554035
|
entity |
| Predicate | novaShellDetected |
P148072
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nova Persei 1901, novaShellDetected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: novaShellDetected Context triple: [Nova Persei 1901, novaShellDetected, true]
-
A.
hasShell
Indicates that an entity possesses or is covered by a shell as a physical protective structure.
-
B.
requiresShellIntegration
Indicates that one entity depends on integration with a command-line or operating system shell environment in order for the related action or functionality to work.
-
C.
typicalShells
Indicates that the associated shells are characteristic or commonly found for the given entity or category.
-
D.
shellFeature
Indicates that one entity functions as a characteristic or structural feature of another entity’s shell.
-
E.
estimatedShellCount
Indicates the estimated number of shells associated with or attributed to an entity.
- F. None of above. chosen
Provenance (4 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.