Triple
T5079671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow Road |
E114482
|
entity |
| Predicate | inspiredFanWorks |
P42754
|
FINISHED |
| Object | fan art |
—
|
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: fan art | Statement: [Rainbow Road, inspiredFanWorks, fan art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredFanWorks Context triple: [Rainbow Road, inspiredFanWorks, fan art]
-
A.
inspiredWorks
chosen
Indicates that one work served as a source of inspiration or creative influence for the creation or development of another work.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
D.
originalTitleAsFanFiction
Indicates that a work’s original title was used when it was first created or published as fan fiction.
-
E.
inspiredTrope
Indicates that one trope serves as the creative or conceptual inspiration for another trope.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f86c988190aa026073ed435a45 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.