Triple
T37158745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannon |
E920585
|
entity |
| Predicate | featuredCrossoverWith |
P8704
|
FINISHED |
| Object | Barnaby Jones |
E618144
|
NE 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: Barnaby Jones | Statement: [Cannon, featuredCrossoverWith, Barnaby Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCrossoverWith Context triple: [Cannon, featuredCrossoverWith, Barnaby Jones]
-
A.
portrayedInCrossover
Indicates that an entity is depicted or appears as a character within a crossover work that combines elements from multiple distinct sources or franchises.
-
B.
featuresCrossoverWith
chosen
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
C.
hasCrossoverAppearancesIn
Indicates that an entity appears in crossover events or stories within the specified work or series.
-
D.
franchiseCrossover
Indicates a relationship where characters, elements, or storylines from one fictional franchise appear within or interact with those of another franchise.
-
E.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
- F. None of above.
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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40360b7c388190885e2db6a514d1b2 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.