Triple
T29077746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fight 3 |
E735986
|
entity |
| Predicate | characterReturn |
P192356
|
FINISHED |
| Object | Guy |
—
|
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: Guy | Statement: [Final Fight 3, characterReturn, Guy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterReturn Context triple: [Final Fight 3, characterReturn, Guy]
-
A.
characterReturnFrom
Indicates that a character comes back to a prior location, situation, or state after having been away or absent.
-
B.
featuresReturningCharacterFrom
chosen
Indicates that a work includes the reappearance of a character who previously appeared in the referenced source work.
-
C.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 28, 2026, 10:24 a.m.