Triple
T25618032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberto Durán in the 1980 "No Más" rematch |
E642210
|
entity |
| Predicate | famousPhraseAssociated |
P132994
|
FINISHED |
| Object | No más |
—
|
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: No más | Statement: [Roberto Durán in the 1980 "No Más" rematch, famousPhraseAssociated, No más]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousPhraseAssociated Context triple: [Roberto Durán in the 1980 "No Más" rematch, famousPhraseAssociated, No más]
-
A.
famousLineSpeaker
Indicates that the subject is the person who spoke or delivered the famous line referenced by the object.
-
B.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
C.
isFamousExcerptOf
Indicates that one text passage is a well-known or widely recognized excerpt taken from a larger work.
-
D.
typicalPhrase
chosen
Indicates that the object is a phrase commonly or characteristically used in connection with the subject.
-
E.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e8734c8190a214685b1647abe1 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:01 p.m.