Triple
T35808625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Legend Killer |
E1035167
|
entity |
| Predicate | developedReputationFor |
P19903
|
FINISHED |
| Object | attacking opponents after matches |
—
|
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: attacking opponents after matches | Statement: [The Legend Killer, developedReputationFor, attacking opponents after matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedReputationFor Context triple: [The Legend Killer, developedReputationFor, attacking opponents after matches]
-
A.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
reputationBuiltFor
chosen
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
C.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
developerReputation
Indicates the perceived trustworthiness, reliability, and quality of work associated with a developer based on their past actions or contributions.
-
E.
denotesReputationOf
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:06 p.m.