Triple
T10324157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky "Jupe" Park |
E242716
|
entity |
| Predicate | usesPastFameFor |
P93373
|
FINISHED |
| Object | promoting Jupiter's Claim |
—
|
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: promoting Jupiter's Claim | Statement: [Ricky "Jupe" Park, usesPastFameFor, promoting Jupiter's Claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPastFameFor Context triple: [Ricky "Jupe" Park, usesPastFameFor, promoting Jupiter's Claim]
-
A.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
B.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
C.
famePeak
Indicates the time or point at which an entity reaches its highest level of fame or public recognition.
-
D.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
-
E.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:51 a.m.