Triple
T10122557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Cohen |
E223330
|
entity |
| Predicate | hasRoleInProduction |
P36865
|
FINISHED |
| Object | producer |
—
|
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: producer | Statement: [Dan Cohen, hasRoleInProduction, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInProduction Context triple: [Dan Cohen, hasRoleInProduction, producer]
-
A.
hasProductionRole
chosen
Indicates that an entity holds a specific role or function in the production or creation process of another entity.
-
B.
hasProductionStatus
Indicates the current stage or condition of an entity’s production process (e.g., planned, in progress, completed, or discontinued).
-
C.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
D.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
-
E.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd26846b8819098594bf211920eb2 |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.