Triple
T18552082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Stella |
E453401
|
entity |
| Predicate | remnantDetected |
P132126
|
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 Stella, remnantDetected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remnantDetected Context triple: [Nova Stella, remnantDetected, true]
-
A.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
B.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
C.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
D.
remnantName
Indicates that an entity is identified by a name specifically associated with a remaining part, leftover, or surviving fragment of something previously whole.
-
E.
describesRemnant
Indicates that one entity provides a description or characterization of another entity that is a remaining part, leftover, or surviving trace of something previously whole or present.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538019a74819099dbd255fb21fa95 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.