Triple
T12186451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There and Back Again |
E290346
|
entity |
| Predicate | inUniverseAuthorRace |
P97512
|
FINISHED |
| Object | Hobbit |
—
|
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: Hobbit | Statement: [There and Back Again, inUniverseAuthorRace, Hobbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseAuthorRace Context triple: [There and Back Again, inUniverseAuthorRace, Hobbit]
-
A.
inUniverseOwnerSpecies
Indicates that a particular species is recognized as the canonical or in-universe owner of something within a fictional or defined universe.
-
B.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
inUniverseRaceOfReferent
chosen
Indicates that the referent belongs to, or is a member of, a particular race within a specified fictional or conceptual universe.
-
D.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
E.
workAuthoredInUniverse
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.