Triple
T37602425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood glamour |
E935559
|
entity |
| Predicate | hasNotableIcon |
P88883
|
FINISHED |
| Object | Marilyn Monroe |
E16840
|
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: Marilyn Monroe | Statement: [Hollywood glamour, hasNotableIcon, Marilyn Monroe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIcon Context triple: [Hollywood glamour, hasNotableIcon, Marilyn Monroe]
-
A.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
B.
hasNotableItem
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
C.
hasIcons
chosen
Indicates that one entity possesses, includes, or is associated with one or more icons in relation to another entity or context.
-
D.
hasMarketingIcon
Indicates that an entity is associated with, or represented by, a specific marketing-related icon or symbol.
-
E.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afdf21b08190931b6be0f6c105d9 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.