Triple
T14014892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unforgettable |
E337177
|
entity |
| Predicate | hasCommercialAppeal |
P112464
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Unforgettable, hasCommercialAppeal, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommercialAppeal Context triple: [Unforgettable, hasCommercialAppeal, high]
-
A.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
B.
hasCommercialPerformance
Indicates that an entity’s success or outcome is characterized in terms of its performance in the commercial or market context (e.g., sales, revenue, or profitability).
-
C.
hasCommercialField
Indicates that one entity possesses or is associated with a commercial-related field, area, or domain in relation to another entity.
-
D.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
-
E.
hasCommercialAxis
Indicates that there exists a primary direction, route, or area along which commercial or business activities are concentrated or organized.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.