Triple
T32641303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zatoichi |
E834484
|
entity |
| Predicate | crossOverWith |
P51996
|
FINISHED |
| Object | Yojimbo franchise |
—
|
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: Yojimbo franchise | Statement: [Zatoichi, crossOverWith, Yojimbo franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossOverWith Context triple: [Zatoichi, crossOverWith, Yojimbo franchise]
-
A.
crossesOverWith
chosen
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
B.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
-
C.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
D.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
E.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:07 a.m.