Triple
T24725780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnaby Jones |
E618144
|
entity |
| Predicate | spinOffOrCrossoverWith |
P51499
|
FINISHED |
| Object | Cannon |
—
|
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: Cannon | Statement: [Barnaby Jones, spinOffOrCrossoverWith, Cannon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffOrCrossoverWith Context triple: [Barnaby Jones, spinOffOrCrossoverWith, Cannon]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
spinOffWork
chosen
Indicates that one work is derived from, based on, or created as a spin-off of another preexisting work.
-
C.
spinoffRelation
Indicates a relationship where one entity originates as a derivative, offshoot, or spin-off from another entity.
-
D.
spinoffMemberOf
Indicates that one entity originated as a spinoff from, and is organizationally or historically derived from, another entity.
-
E.
spinOffNetwork
Indicates that a new network entity has been created as a derivative or offshoot of an existing network.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:57 a.m.