Triple
T29963959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My People |
E761120
|
entity |
| Predicate | hasGlobalChartSuccess |
P168717
|
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: [My People, hasGlobalChartSuccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalChartSuccess Context triple: [My People, hasGlobalChartSuccess, true]
-
A.
hasChartSuccessWith
Indicates that an entity has achieved measurable success on music or performance charts in connection with another specified entity.
-
B.
hasChartStatus
Indicates that an entity is associated with a particular chart-related state or condition (e.g., its current status within a chart or dashboard).
-
C.
hasChart
Indicates that one entity is associated with, represented by, or documented through a chart belonging to or describing it.
-
D.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
E.
hasChartingVersion
Indicates that one entity is associated with a specific version of charting or visualization used to represent its data or configuration.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67867c7d481908de3db59b2bd7768 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:29 p.m.