Triple
T14191464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold Chillin' Records |
E351721
|
entity |
| Predicate | notableRoster |
P63184
|
FINISHED |
| Object | Juice Crew members |
—
|
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: Juice Crew members | Statement: [Cold Chillin' Records, notableRoster, Juice Crew members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRoster Context triple: [Cold Chillin' Records, notableRoster, Juice Crew members]
-
A.
notableMemberOfRoster
Indicates that an entity is a distinguished or prominent member within a particular roster or lineup.
-
B.
notableLineup
chosen
Indicates that an entity is recognized as part of a particularly significant or distinguished group, roster, or cast associated with another entity.
-
C.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
D.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
E.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61df628c8190ba3f557e2128dce5 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:04 a.m.