Triple
T5160268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rollout (My Business) |
E116417
|
entity |
| Predicate | chartStatus |
P62296
|
FINISHED |
| Object | commercially successful |
—
|
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: commercially successful | Statement: [Rollout (My Business), chartStatus, commercially successful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartStatus Context triple: [Rollout (My Business), chartStatus, commercially successful]
-
A.
chartSuccessWith
Indicates a relationship where one entity measures, tracks, or visualizes the success or performance of another entity using charts or similar representations.
-
B.
chartingSingle
Indicates that an entity appears on a music chart as a single track release.
-
C.
chartName
Indicates the specific title or label assigned to a chart that identifies or describes it.
-
D.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
E.
chartType
Indicates the specific kind or category of chart used to visually represent data in a given context.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79bf9b088190a556dc02f10204e4 |
completed | March 20, 2026, 4:45 p.m. |
Created at: March 20, 2026, 1:44 p.m.