Triple
T35263597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop Ya Collar |
E1018442
|
entity |
| Predicate | leakedBeforeOfficialRelease |
P111490
|
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: [Pop Ya Collar, leakedBeforeOfficialRelease, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leakedBeforeOfficialRelease Context triple: [Pop Ya Collar, leakedBeforeOfficialRelease, true]
-
A.
specificationLeakedIn
Indicates that the details or specifications of something have been disclosed or exposed within a particular context, location, or medium without proper authorization.
-
B.
hasUnofficialRelease
chosen
Indicates that an entity has a release or version that exists or is distributed outside of official or formally recognized channels.
-
C.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
D.
leakDate
Indicates the date on which something (such as information, content, or a product) became publicly known or was unofficially released.
-
E.
releasedBefore
Indicates that one entity was released at an earlier time or date than 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f724efc81908ffd4e5700701e3b |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.