Triple
T26758962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orgy Island |
E674745
|
entity |
| Predicate | eraOfNotoriety |
P71040
|
FINISHED |
| Object | post‑2019 media coverage |
—
|
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: post‑2019 media coverage | Statement: [Orgy Island, eraOfNotoriety, post‑2019 media coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfNotoriety Context triple: [Orgy Island, eraOfNotoriety, post‑2019 media coverage]
-
A.
hasMannerOfNotoriety
Indicates that an entity is known or recognized in a particular way, specifying the manner or type of its notoriety.
-
B.
genreOfNotoriety
Indicates that an entity is known or famous specifically for a particular genre or category.
-
C.
inceptionOfNotoriety
chosen
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
D.
notoriouslyAssociatedWith
Indicates a widely recognized and often negative or infamous association between one entity and another.
-
E.
notableAdversary
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
- F. None of above.
Provenance (3 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:57 a.m.