Triple
T33404650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordy's Home |
E855404
|
entity |
| Predicate | inUniverseFame |
P183753
|
FINISHED |
| Object | infamous for on-set tragedy |
—
|
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: infamous for on-set tragedy | Statement: [Gordy's Home, inUniverseFame, infamous for on-set tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseFame Context triple: [Gordy's Home, inUniverseFame, infamous for on-set tragedy]
-
A.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
isMoreFamousThan
Indicates that one entity is better known or more widely recognized by people than another entity.
-
C.
basedOnFameFrom
Indicates that something is determined, influenced, or derived from the level or source of fame associated with an entity.
-
D.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
E.
basisInUniverse
Indicates that one entity serves as the foundational basis or underlying grounding for another entity within a given universe or domain.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 1, 2026, 1:36 a.m.