Triple
T20844908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Sciarra |
E513194
|
entity |
| Predicate | Cold Brew LabsRole |
P142061
|
FINISHED |
| Object | co-founder |
—
|
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: co-founder | Statement: [Paul Sciarra, Cold Brew LabsRole, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Cold Brew LabsRole Context triple: [Paul Sciarra, Cold Brew LabsRole, co-founder]
-
A.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
B.
hasBreweryFocus
Indicates that an entity (such as a business, product, or activity) is primarily oriented around, specialized in, or dedicated to breweries or brewing-related operations.
-
C.
coffeeBrand
Indicates that one entity is a brand associated with the production or marketing of coffee products for the other entity.
-
D.
notableBrewmaster
Indicates that an entity is recognized for being an outstanding or distinguished brewmaster, typically noted for significant skill, influence, or achievement in brewing.
-
E.
knownBrewer
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34deef88190992b959b83bc59b1 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.