Triple
T36071853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bless Yo Trap |
E1043388
|
entity |
| Predicate | hasTrackWith |
P201223
|
FINISHED |
| Object | Lil Yachty |
—
|
NE NERFINISHED |
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: Lil Yachty | Statement: [Bless Yo Trap, hasTrackWith, Lil Yachty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackWith Context triple: [Bless Yo Trap, hasTrackWith, Lil Yachty]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasTrackControl
Indicates that one entity has authority or capability to manage, direct, or regulate the operation or behavior of another entity’s track or tracking process.
-
C.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
D.
hasTrackSection
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
-
E.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_69ffdf46e18c8190a5e4f4e5211cb087 |
completed | May 10, 2026, 1:28 a.m. |
Created at: May 3, 2026, 4:08 p.m.