Triple
T22801788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Je-hyuk |
E564412
|
entity |
| Predicate | popularityInStory |
P149770
|
FINISHED |
| Object | famous professional athlete |
—
|
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: famous professional athlete | Statement: [Kim Je-hyuk, popularityInStory, famous professional athlete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityInStory Context triple: [Kim Je-hyuk, popularityInStory, famous professional athlete]
-
A.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
C.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
D.
popularFrom
Indicates that something gains or holds popularity starting from a specific time, source, or context.
-
E.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
- F. None of above. chosen
Provenance (4 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdd87648190ba30f0b8f3ef7346 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:31 p.m.