Triple
T36060570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxer Santaros |
E1043065
|
entity |
| Predicate | hasAlternateNameInStory |
P83029
|
FINISHED |
| Object | Jericho Cane |
—
|
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: Jericho Cane | Statement: [Boxer Santaros, hasAlternateNameInStory, Jericho Cane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateNameInStory Context triple: [Boxer Santaros, hasAlternateNameInStory, Jericho Cane]
-
A.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
B.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
C.
hasAlternativeEditionTitle
Indicates that an entity has a different or variant title used in another edition of the same work.
-
D.
hasFictionalAlias
chosen
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
E.
hasAlternativeNamesakeRole
Indicates that an entity serves in an additional or alternative role as a namesake, distinct from its primary namesake role.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:08 p.m.