Triple
T7207217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldie |
E148695
|
entity |
| Predicate | helpedCement |
P33868
|
FINISHED |
| Object | ASAP Rocky early mainstream success |
—
|
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: ASAP Rocky early mainstream success | Statement: [Goldie, helpedCement, ASAP Rocky early mainstream success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedCement Context triple: [Goldie, helpedCement, ASAP Rocky early mainstream success]
-
A.
cementType
Indicates the specific kind or classification of cement associated with an entity.
-
B.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
C.
helpsProduce
Indicates that one entity contributes to or facilitates the creation, generation, or production of another entity.
-
D.
ledToConstructionOf
Indicates that one entity caused, initiated, or was the primary reason for the construction or creation of another entity.
-
E.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
- F. None of above.
Provenance (3 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e969c5fc819096bc03bfba12d0cf |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.