Triple
T29229683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatal Fury Special |
E741032
|
entity |
| Predicate | crossoverFrom |
P175249
|
FINISHED |
| Object | Art of Fighting |
—
|
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: Art of Fighting | Statement: [Fatal Fury Special, crossoverFrom, Art of Fighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossoverFrom Context triple: [Fatal Fury Special, crossoverFrom, Art of Fighting]
-
A.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
B.
crossoverWork
chosen
Indicates that a work features a crossover, combining characters, settings, or elements from two or more distinct works or franchises into a single creative piece.
-
C.
crossedFrom
Indicates that an entity moved across a boundary or dividing line starting from a specified origin location or side.
-
D.
featuresCrossoverWith
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
E.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 12:18 p.m.