Triple
T38305598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young, Rich & Dangerous |
E1032335
|
entity |
| Predicate | hasMatureImageComparedTo |
P81371
|
FINISHED |
| Object | Totally Krossed Out |
E1032334
|
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: Totally Krossed Out | Statement: [Young, Rich & Dangerous, hasMatureImageComparedTo, Totally Krossed Out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatureImageComparedTo Context triple: [Young, Rich & Dangerous, hasMatureImageComparedTo, Totally Krossed Out]
-
A.
hasMatureStyleComparedTo
Indicates that one entity exhibits a more developed, refined, or advanced style in comparison to another entity.
-
B.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
-
C.
hasMatureSoundComparedTo
chosen
Indicates that one entity’s sound is considered more mature or developed in quality when compared to another entity’s sound.
-
D.
hasMaturityType
Indicates that an entity is associated with a specific type or category of maturity it possesses or reaches.
-
E.
hasMaturityDate
Indicates the date on which an obligation, instrument, or agreement is scheduled to become due or reach the end of its term.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea7742c48190a2e1638dccb76814 |
completed | June 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.