Triple
T33209475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space (novel) |
E850109
|
entity |
| Predicate | hasFictionalizedVersionsOf |
P191964
|
FINISHED |
| Object | NASA astronauts |
—
|
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: NASA astronauts | Statement: [Space (novel), hasFictionalizedVersionsOf, NASA astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalizedVersionsOf Context triple: [Space (novel), hasFictionalizedVersionsOf, NASA astronauts]
-
A.
hasFictionalDepictions
chosen
Indicates that an entity is represented or portrayed in one or more fictional works or narratives.
-
B.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
hasFictionalSeries
Indicates that one entity is a fictional series that another entity possesses, is associated with, or is the creator/owner of.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
hasFictionalDescendants
Indicates that an entity is the ancestor of one or more descendants that exist only within a fictional or imaginary context.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:30 a.m.