Triple
T28969065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kylos |
E734221
|
entity |
| Predicate | fictionalNature |
P187379
|
FINISHED |
| Object | imaginary astronomical object |
—
|
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: imaginary astronomical object | Statement: [Kylos, fictionalNature, imaginary astronomical object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalNature Context triple: [Kylos, fictionalNature, imaginary astronomical object]
-
A.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
B.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
C.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
D.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
E.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 28, 2026, 9:04 a.m.