Triple
T35051798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Barnes |
E1011347
|
entity |
| Predicate | nicknameInFandom |
P23575
|
FINISHED |
| Object | Karate’s Bad Boy |
—
|
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: Karate’s Bad Boy | Statement: [Mike Barnes, nicknameInFandom, Karate’s Bad Boy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameInFandom Context triple: [Mike Barnes, nicknameInFandom, Karate’s Bad Boy]
-
A.
fandomNickname
chosen
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
B.
nicknameCoinedIn
Indicates that a particular nickname was first created, introduced, or came into use in a specified time or context.
-
C.
nicknameExplained
Indicates that an entity’s nickname is clarified, justified, or given context by another piece of information.
-
D.
lineNickname
Indicates that one entity is an alternative or informal name (nickname) used to refer to a particular line (such as a route, service, or connection).
-
E.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.