Triple
T29121101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jirel of Joiry stories |
E737183
|
entity |
| Predicate | crossoverWork |
P175249
|
FINISHED |
| Object | Quest of the Starstone |
—
|
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: Quest of the Starstone | Statement: [Jirel of Joiry stories, crossoverWork, Quest of the Starstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossoverWork Context triple: [Jirel of Joiry stories, crossoverWork, Quest of the Starstone]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
collaborativeWork
Indicates a relationship where two or more entities jointly contribute effort or resources toward a shared task, project, or goal.
-
C.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
D.
worksAgainst
Indicates that one entity actively opposes, counteracts, or undermines the goals, effects, or interests of another entity.
-
E.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 11:25 a.m.