Triple
T38060920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riley |
E950336
|
entity |
| Predicate | prominentInMarketing |
P189923
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Riley, prominentInMarketing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentInMarketing Context triple: [Riley, prominentInMarketing, true]
-
A.
notableMarketPositioning
Indicates that an entity holds a distinctive or strategically significant position within a particular market or competitive landscape.
-
B.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
C.
isOneOfMostProminentIn
Indicates that an entity ranks among the most notable, influential, or widely recognized members within a specified group, category, or domain.
-
D.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
E.
marketedWith
Indicates that two or more products or services are promoted together as part of the same marketing effort or campaign.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:21 p.m.