Triple
T34146308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Omar: Greatest Hits |
E875867
|
entity |
| Predicate | includesPopularTracksFrom |
P5071
|
FINISHED |
| Object | The Last Don |
E871971
|
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: The Last Don | Statement: [Don Omar: Greatest Hits, includesPopularTracksFrom, The Last Don]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPopularTracksFrom Context triple: [Don Omar: Greatest Hits, includesPopularTracksFrom, The Last Don]
-
A.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
B.
sharesTracksWith
chosen
Indicates that two entities have one or more tracks in common, such as shared audio, rail, or route segments.
-
C.
trackIncluded
Indicates that a particular track is contained within, or forms part of, a larger collection, release, or grouping of tracks.
-
D.
isPopularRecordingOf
Indicates that one entity is a widely known or frequently enjoyed version or performance of another work, such as a song or composition.
-
E.
hasFanFavoriteTrack
Indicates that an entity is associated with a track that is especially popular or favored by fans.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5d1cf48819082fd3f8e666f2c09 |
completed | June 20, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.