Triple
T31734406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knots and Crosses |
E809952
|
entity |
| Predicate | seriesLaunches |
P140701
|
FINISHED |
| Object | Inspector Rebus series |
—
|
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: Inspector Rebus series | Statement: [Knots and Crosses, seriesLaunches, Inspector Rebus series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesLaunches Context triple: [Knots and Crosses, seriesLaunches, Inspector Rebus series]
-
A.
launchesSeries
chosen
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
-
B.
studioRelease
Indicates that a work (such as a film, album, or game) is officially released or distributed by a particular studio.
-
C.
releaseSeries
Indicates that one entity publishes or makes available a sequence of related releases (such as episodes, issues, or installments) as part of an ongoing series.
-
D.
commercialLaunchFirst
Indicates that this event marks the first commercial launch associated with the subject entity.
-
E.
screenGemsRelease
Indicates that the subject was released or distributed by Screen Gems.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 30, 2026, 11:22 p.m.