Triple
T35623305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cry |
E1029375
|
entity |
| Predicate | firstMadeFamousBy |
P55021
|
FINISHED |
| Object | Johnnie Ray |
E315145
|
NE 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: Johnnie Ray | Statement: [Cry, firstMadeFamousBy, Johnnie Ray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMadeFamousBy Context triple: [Cry, firstMadeFamousBy, Johnnie Ray]
-
A.
madeInternationallyFamousBy
Indicates that one entity became widely known across multiple countries as a result of the actions, influence, or association of another entity.
-
B.
starMadeFamous
Indicates that one entity (such as a work, event, or role) is what caused another entity (typically a person) to become widely known or famous.
-
C.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
D.
songMadeFamousBy
chosen
Indicates that a song became widely known or popular primarily through the performance, recording, or promotion of a particular artist or group.
-
E.
madeFamousByFilm
Indicates that something became widely known or gained significant public recognition as a result of being featured in a film.
- F. None of above.
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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389c03b900819099674f6db2d59500 |
completed | June 22, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.