Triple
T37469133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A City Sleeps |
E931107
|
entity |
| Predicate | developerPreviousWorks |
P115212
|
FINISHED |
| Object | Rock Band series |
—
|
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: Rock Band series | Statement: [A City Sleeps, developerPreviousWorks, Rock Band series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerPreviousWorks Context triple: [A City Sleeps, developerPreviousWorks, Rock Band series]
-
A.
designerPreviouslyWorkedOn
Indicates that a designer has worked on the same or a related project in the past, prior to the current context or engagement.
-
B.
laterCareerWorkOf
Indicates that one work represents a creator’s later career output in relation to another work or to their overall body of work.
-
C.
projectsOn
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain of another entity.
-
D.
workRepresented
Indicates that one entity is a representation (such as a depiction, adaptation, or portrayal) of another work.
-
E.
previousWorkByProducer
chosen
Indicates that a work was created earlier by the same producer responsible for another referenced work.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:17 p.m.