Triple
T25618053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberto Durán in the 1980 "No Más" rematch |
E642210
|
entity |
| Predicate | phraseMeaningInEnglish |
P103900
|
FINISHED |
| Object | No more |
—
|
LITERAL FINISHED |
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 more | Statement: [Roberto Durán in the 1980 "No Más" rematch, phraseMeaningInEnglish, No more]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phraseMeaningInEnglish Context triple: [Roberto Durán in the 1980 "No Más" rematch, phraseMeaningInEnglish, No more]
-
A.
meaningOfPhrase
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
B.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
C.
textMeaning
chosen
Indicates that one text expresses, conveys, or corresponds to a particular meaning or semantic content.
-
D.
apMeaning
Indicates that one entity expresses, conveys, or signifies the meaning or semantic content of another entity.
-
E.
wordByWordMeaning
Indicates a relationship where the detailed meaning of a phrase or sentence is given separately for each individual word.
- 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_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:01 p.m.