Triple
T29119786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far Star |
E737147
|
entity |
| Predicate | authorUniverse |
P115764
|
FINISHED |
| Object | Isaac Asimov |
—
|
NE NERFINISHED |
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: Isaac Asimov | Statement: [Far Star, authorUniverse, Isaac Asimov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorUniverse Context triple: [Far Star, authorUniverse, Isaac Asimov]
-
A.
fictionalUniverseAuthor
chosen
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
B.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
C.
otherIn-universeAuthors
Indicates that one entity is an author or creator of works within the fictional universe of another entity.
-
D.
workAuthoredInUniverse
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
E.
createdInUniverseBy
Indicates that something was brought into existence within a particular fictional or conceptual universe by a specific creator or originating agent.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 11:24 a.m.